public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha•warpmail.net>
To: Tim Mazid <timmazid@hotmail•com>
Cc: git@vger•kernel.org
Subject: Re: Headless tags don't have a follows or precedes?
Date: Mon, 02 Nov 2009 10:42:07 +0100	[thread overview]
Message-ID: <4AEEA96F.7080609@drmicha.warpmail.net> (raw)
In-Reply-To: <1257067898626-3926483.post@n2.nabble.com>

Tim Mazid venit, vidit, dixit 01.11.2009 10:31:
> 
> Hi all,
> 
> I've noticed that if I create a headless tag (one that doesn't have a
> branch, right?), when I click on that commit, it doesn't have precedes or
> follows information. Is this by design? Is there a work-around I can use
> without creating a branch there?

Reposting (without even saying so) doesn't necessarily increase your
chance of getting responses. Would would help:

- saying you're talking about gitk/git view/whatever it is you're
"clicking" on

- providing a minimal example others can reproduce. That would be one
where a tag on a detached head (assuming that's what you mean) has no
precedes/follow but a tag "on a branch" does have that info

Cheers,
Michael

  reply	other threads:[~2009-11-02  9:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01  9:31 Headless tags don't have a follows or precedes? Tim Mazid
2009-11-02  9:42 ` Michael J Gruber [this message]
2009-11-02 13:07   ` Tim Mazid
2009-11-02 15:54     ` Michael J Gruber
2009-11-20  1:07       ` Tim Mazid
  -- strict thread matches above, loose matches on Subject: below --
2009-10-28 11:36 Tim Mazid
2009-11-02 13:09 ` Dmitry Potapov
2009-11-02 13:16   ` 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=4AEEA96F.7080609@drmicha.warpmail.net \
    --to=git@drmicha$(echo .)warpmail.net \
    --cc=git@vger$(echo .)kernel.org \
    --cc=timmazid@hotmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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