On 1/6/15, Ron W <[email protected]> wrote: > On Tue, Jan 6, 2015 at 4:04 AM, Stephan Beal <[email protected]> wrote: > >> >> agreed. AFAIK, branches currently do not use the VALUE part of the tag. >> Perhaps such a description could be set there when making a branch, e.g.: >> >> >> fossil commit -b new-branch -d "branch description" -m "commit message" >> >> That would require no incompatible changes (provided i'm correct about >> branch tags not having a value). >> > > Looking at Fossil's time line, branches appear to have 2 propagating tags: > > branch=name > sym-name > > The "sym-" one not having a value. Strange to me that 2 tags would be used >
The sym-name tag is there so that command like "fossil update trunk" will be able to resolve the name "trunk" to be the most recent check-in with the "sym-trunk" tag, which is also the latest trunk check-in. -- D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
