> > Would it be too difficult to put the branch tag (i.e the tag with asterisk > > from > 'fossil br li' output) in the first line of manifest.tags? > > It probably wouldn't, but I've been trying to keep the code agnostic with > regards to being used in a checkout or not. The "current branch tag" is not > applicable when generating archives from the web ui, for instance.
I didn't mean the current checkout branch tag, just used that as an example. I meant branch tag of the check-in you're getting the source from, i.e. what's in the manifest.uuid. > Is this not sufficient for your needs? I'm not completely opposed to > implementing what you're asking for, but if it can already be done without > adding a "within a checkout" special case, I would prefer to leave it as it > is. I don't think you need such a special case. Maybe a better way is to extract raw tags, or provide an option to do so, because then the branch tag is easily distinguished: C:\Temp>f timeline -t ci -R t.fossil === 2016-01-05 === 08:02:44 [11a34d67d0] Branch (user: Steve tags: test_branch, branch_tag) === 2015-12-27 === 02:45:54 [0a1fb00ed9] initial empty check-in (user: Steve tags: trunk, trunk_tag) +++ no more data (2) +++ C:\Temp>f tag list --raw trunk -R t.fossil branch=trunk sym-trunk sym-trunk_tag C:\Temp>f tag list --raw test_branch -R t.fossil branch=test_branch sym-branch_tag sym-test_branch sym-trunk Cheers, Steve _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
