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:07:27 -0800 (PST)	[thread overview]
Message-ID: <1257167247221-3931674.post@n2.nabble.com> (raw)
In-Reply-To: <4AEEA96F.7080609@drmicha.warpmail.net>



Michael J Gruber-2 wrote:
> 
> 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.
> 
I didn't repost. Or at the least, I didn't mean to repost. The mailing list
kept complaining (spamming me) that my post was pending, and I eventually
realised that was the old forum. I deleted it from there, and copy-pasted
here. I didn't even realise it had posted here, and that when I deleted from
the old forum, it didn't delete here.


Michael J Gruber-2 wrote:
> 
> Would would help:
> 
> - saying you're talking about gitk/git view/whatever it is you're
> "clicking" on
> 
My apologies, yes, in gitk.


Michael J Gruber-2 wrote:
> 
> - 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
> 

Example (unless specified, commands as entered into bash)

mkdir temp
cd temp
git init
gitk --all &
git commit --allow-empty -m '1'
git tag v1
git commit --allow-empty -m '1.1'
git tag v1.1
git commit --allow-empty -m '1.2'
git tag v1.2
(in gitk, press ctrl+f5; all follows and precedes info is there)
git checkout v1.1
git commit --allow-empty -m '1.1.1'
git tag v1.1.1
(in gitk, press f5; follows and precedes info missing for v1.1 and v1.1.1)
(close gitk)
gitk --all &
(info still missing)
git commit --allow-empty -m '1.1.2'
git tag v1.1.2
(in gitk, press f5, info still missing)
git checkout master
git commit --allow-empty -m '1.3'
git tag v1.3
(in gitk, press f5, info still missing)
git commit --allow-empty -m '1.4'
git tag v1.4
(in gitk, press f5, info still missing)
git checkout -b temp v1.2
git commit --allow-empty -m '1.2.1'
git tag v1.2.1
(in gitk, press f5, info still missing)
git checkout master
git branch -D temp
git commit --allow-empty -m '1.5'
git tag v1.5
(in gitk, press f5, info still missing)


In the end, the only follows/precedes info is:
v1: precedes v1.1
v1.1: follows v1, precedes v1.2
v1.2: follows v1.1
All the rest is missing.
-- 
View this message in context: http://n2.nabble.com/Headless-tags-don-t-have-a-follows-or-precedes-tp3926483p3931674.html
Sent from the git mailing list archive at Nabble.com.

  reply	other threads:[~2009-11-02 13:07 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
2009-11-02 13:07   ` Tim Mazid [this message]
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=1257167247221-3931674.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).