From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git-pull and tag objects
Date: Thu, 15 Feb 2007 02:21:36 +0100 [thread overview]
Message-ID: <er0cfg$1m7$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0702132230490.3604@woody.linux-foundation.org
Linus Torvalds wrote:
> One thing that _might_ be a good idea for tags (if people _really_ want to
> actually update tags under the same name) is to have a "parent" pointer
> for tag objects, the same way we have for commits. That way you could - if
> you really wanted to - create a chain of tags, and show the history of
> them.
Wouldn't it be better to just use reflog for given tag? That assuming of
course that we could protect tag reflog from pruning...
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-02-15 1:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 11:16 git-pull and tag objects Alex Bennee
2007-02-09 9:33 ` Alex Riesen
2007-02-09 23:19 ` Junio C Hamano
2007-02-10 0:14 ` [PATCH] git-fetch: document automatic tag following Junio C Hamano
2007-02-10 14:23 ` git-pull and tag objects Theodore Tso
2007-02-10 17:56 ` Linus Torvalds
2007-02-10 21:32 ` Jakub Narebski
2007-02-10 21:58 ` Linus Torvalds
2007-02-11 21:55 ` Junio C Hamano
2007-02-12 0:40 ` Jakub Narebski
2007-02-11 0:25 ` Theodore Tso
2007-02-11 3:21 ` Linus Torvalds
2007-02-11 5:52 ` Junio C Hamano
2007-02-11 17:49 ` Linus Torvalds
2007-02-11 19:17 ` Junio C Hamano
2007-02-11 19:21 ` Junio C Hamano
2007-02-11 19:25 ` Linus Torvalds
2007-02-11 21:41 ` Junio C Hamano
2007-02-12 16:27 ` Theodore Tso
2007-02-13 6:17 ` Junio C Hamano
2007-02-14 6:38 ` Linus Torvalds
2007-02-14 7:22 ` Junio C Hamano
2007-02-14 11:18 ` Johannes Schindelin
2007-02-14 16:35 ` Linus Torvalds
2007-02-15 1:21 ` Jakub Narebski [this message]
2007-02-15 1:34 ` Johannes Schindelin
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='er0cfg$1m7$1@sea.gmane.org' \
--to=jnareb@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).