git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Mazid <timmazid@hotmail.com>
To: git@vger.kernel.org
Subject: Re: Headless tags don't have a follows or precedes?
Date: Mon, 2 Nov 2009 05:16:28 -0800 (PST)	[thread overview]
Message-ID: <1257167788750-3931717.post@n2.nabble.com> (raw)
In-Reply-To: <20091102130919.GB27126@dpotapov.dyndns.org>



Dmitry Potapov wrote:
> 
> I have never heard tag being described as headless... A tag is just a
> pointer on some commit (annotated tag contains additional information
> such as creater, data, message), in any case, it has no direct relation
> to any branch.
> 
> Tags do not store any precedes or follows information, no matter how you
> created them, but visualization tools can look at the tree and display
> what was before some commit and what was after it. Without seeing your
> tree, it is impossible to tell whether gitk (or what you use?) displayed
> that correctly or not.
> 
Well, not the tag itself, but the commit the tags points to. Same thing.
Like you're always bothered to say "the commit that the tag v1 points to"
rather than "the v1 tag".
Also, see my post above.
-- 
View this message in context: http://n2.nabble.com/Headless-tags-don-t-have-a-follows-or-precedes-tp3926483p3931717.html
Sent from the git mailing list archive at Nabble.com.

  reply	other threads:[~2009-11-02 13:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-28 11:36 Headless tags don't have a follows or precedes? Tim Mazid
2009-11-02 13:09 ` Dmitry Potapov
2009-11-02 13:16   ` Tim Mazid [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-11-01  9:31 Tim Mazid
2009-11-02  9:42 ` Michael J Gruber
2009-11-02 13:07   ` Tim Mazid
2009-11-02 15:54     ` Michael J Gruber
2009-11-20  1:07       ` Tim Mazid

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=1257167788750-3931717.post@n2.nabble.com \
    --to=timmazid@hotmail.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).