Re: git tag's history

From: Will Palmer <wmpalmer@gmail.com>
Date: Jul 26, 2010, 13:36 UTC
Message-ID: <1280151367.8229.28.camel@wpalmer.simply-domain>
In-Reply-To: <AANLkTikTqJVbohquiNmW0BvP0bXsVFyMw0H4qF2FbhiH@mail.gmail.com>

On Mon, 2010-07-26 at 02:36 -0700, David Aguilar wrote:

Show 5 quoted lines

> 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.