Thus said Stephan Beal on Sun, 07 Sep 2014 17:56:37 +0200: > to assume that all tags passed in this way are "symbolic" tags[1], and > will in fact do non-intuitive things if you try to use: --tag > '*propagating' (with an asterisk in front to make it look like a > propagating tag). IMO the '*' at the front of the name should be > respected to mean "this is a propagating tag," and a '-' at the front > could/should be used to mean "cancel the tag." Potential points for > improvement at some point.
Probably could use some improvement, but aren't these covered already? fossil tag add ?--raw? ?--propagate? TAGNAME CHECK-IN ?VALUE? fossil tag cancel ?--raw? TAGNAME CHECK-IN If I want propagate shouldn't I use --propagate rather than rely on knowing some implementation detail about Fossil's manifest internals? If I do: fossil tag add --propagate '*test' c43801ea69b2292c5ea31732425f69d885e38cd9 It does what I expect. It creates a propagating tag on that checkin that has a * in it's name. Even if I use --raw, I still don't have to know anything about * (but I do have to know the difference between a tag that begins with sym- and one that does not: fossil tag add --raw --propagate 'sym-*test' c43801ea69b2292c5ea31732425f69d885e38cd9 But these things I can learn by looking at a checkin and seeing the raw names of tags. I suppose I can also learn about the fact that * is used in manifests to signify propation. Andy -- TAI64 timestamp: 40000000540c874f _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users