From: Will Palmer <wmpalmer@gmail.com>
To: David Aguilar <davvid@gmail.com>
Cc: Mahesh Vaidya <forvaidya@gmail.com>, git@vger.kernel.org
Subject: Re: git tag's history
Date: Mon, 26 Jul 2010 14:36:07 +0100 [thread overview]
Message-ID: <1280151367.8229.28.camel@wpalmer.simply-domain> (raw)
In-Reply-To: <AANLkTikTqJVbohquiNmW0BvP0bXsVFyMw0H4qF2FbhiH@mail.gmail.com>
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.
next prev parent reply other threads:[~2010-07-26 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 12:12 git tag's history Mahesh Vaidya
2010-07-26 9:36 ` David Aguilar
2010-07-26 13:36 ` Will Palmer [this message]
2010-07-26 14:17 ` Nicolas Sebrecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1280151367.8229.28.camel@wpalmer.simply-domain \
--to=wmpalmer@gmail.com \
--cc=davvid@gmail.com \
--cc=forvaidya@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).