|Title:||diagnostics for fossil tag cancel X Y|
|Last Modified:||2009-11-13 14:18:15|
|Version Found In:||2009-10-11|
When trying to remove a tag (actually I just want to remove it then regenerate it with --propagating set, but I digress) the command "fossil tag cancel X Y" gives no diagnostics when X does not exist. Eg, try "fossil tag cancel XXXXXXX trunk"
drh added on 2009-11-12 16:41:55:
I will convert this to a "feature request" to issue a warning if the tag does not exist in the local repository.
anonymous added on 2009-11-13 02:36:44:
Related question: what if you sync two repos, each of which has tag FOO on commit BAR, but one of the tags is marked --propagate and the other is not. I assume the --propagate marking wins in this case?
The semantics of tag creation/cancelling and syncing repos seems pretty subtle...
drh added on 2009-11-13 14:18:15:
A distributed, disconnected database (such as fossil, but also git, hg, etc) exhibits many surprising behaviors if you are used to working with a localized, monolithic, and always-connected database. This is an inherent property of distributed and disconnected systems, I'm afraid.