On Mon, 2010-07-26 at 02:36 -0700, David Aguilar wrote: > He won't be able to push the tag unless he forcibly deletes your tag first. > > Tags do not have history. This is a non-technical problem. If s/he's > deleting your tags, it's a social problem. > What about enabling the reflog on the shared bare repository? Tags get changed. That's a fact. It's a necessity, no matter what the theoretical model says. Sometimes there's a reason to replace a tag, and when that happens there is sometimes a reason to hang on to the old value. Pretending "it's a social issue" ignores reality, not the least important aspect of which is "social issues happen. How do we avoid losing information in a sane, scalable manner?" Just an example of a tag which could stand to be updated, take a look at: refs/tags/junio-gpg-pub There's at least one thing in there which is out of date. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html