- Appended to comment:
anonymous added on 2009-11-13 01:36:38:
Logically speaking then, there are two kinds of tags: ones used to mark a unique state, and ones used to label features of states. We might call the latter "labels" if we wanted to distinguish them. Since the former use is quite common, I would suggest requiring a flag when the later use is desired, and kicking back an error when a double tag is created without that option. I would also suggest some feedback: "creating tag XXX (number 4; 3 other commits also have tag XXX)"I do understand that unique tags do not play very well with distributed repos and syncs. But warnings generated at sync time, or some other feedback, might catch some subtle errors which would otherwise slip through.
- Appended to comment:
drh added on 2009-11-12 18:42:57:
The ability to put the same tag on multiple check-ins is a feature, not a bug. We use it (for example) on SQLite to tag each release with a "release" tag. See http://www.sqlite.org/src/timeline?t=release. - Change resolution to "Rejected"
- Change status to "Closed"
- Change comment to "It is easy to accidentally tag multiple points with the same tag. Generally this would be due to a typo or other error, so it really should be guarded against. E.g., fossil tag add foo-tag blah fossil tag add foo-tag bleh No error, no warning, oops. (Suggest requiring current tag to be cancelled before allowing a second point to be given the same tag.)"
- Change foundin to "2009.10.11"
- Change private_contact to "6ba147a4218010d3c6ffddc5ed73dc017a44bf3c"
- Change severity to "Minor"
- Change status to "Open"
- Change title to "multiple tagging"
- Change type to "Code_Defect"