git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Potapov <dpotapov@gmail.com>
To: Tim Mazid <timmazid@hotmail.com>
Cc: git@vger.kernel.org
Subject: Re: Headless tags don't have a follows or precedes?
Date: Mon, 2 Nov 2009 16:09:19 +0300	[thread overview]
Message-ID: <20091102130919.GB27126@dpotapov.dyndns.org> (raw)
In-Reply-To: <26093136.post@talk.nabble.com>

On Wed, Oct 28, 2009 at 04:36:59AM -0700, Tim Mazid wrote:
> 
> I've noticed that if I create a headless tag (one that doesn't have a
> branch, right?),

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.

> when I click on that commit, it doesn't have precedes or
> follows information. Is this by design?

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.


Dmitry

  reply	other threads:[~2009-11-02 13:08 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 [this message]
2009-11-02 13:16   ` Tim Mazid
  -- 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=20091102130919.GB27126@dpotapov.dyndns.org \
    --to=dpotapov@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=timmazid@hotmail.com \
    /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).