Thus said Philip Bennefall on Sun, 07 Sep 2014 18:40:32 +0200: > So in summary, it seems that non-propagating tags now show up in the > editor output if they are added as part of the commit command but not > if they are added with tag add.
And that is working as designed. A non-propagating tag exists only on the checkin to which it was applied. It is historical and only applies to that checkin and will never show up in your editor when committing a new checkin unless it was added again with the --tag option. It sounds like you expected --tag to create a propagating tag. At the moment, as Stephan said, there is no way to do this with --tag. There certainly is an argument that there should be, but how should it be implemented? And how much of the underlying tags implementation should it expose? For example, what if I want the tag to not be symbolic and propagating? Currently there exist a few options that add tags: --bgcolor COLOR --branch NEW-BRANCH-NAME --branchcolor COLOR --close --tag Maybe there should be a --propagating-tag option that allows a propagating symbolic tag? Or maybe a more generic --rawtag which allows me to specify all kinds of tags (similar to fossil tag)? Or maybe people who want more than a symbolic tag just use fossil tag? Andy -- TAI64 timestamp: 40000000540c8f4f _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
