git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Headless tags don't have a follows or precedes?

From
TMTim Mazid <timmazid@hotmail.com>
Date
Nov 2, 2009, 13:07 UTC
Message-ID
<1257167247221-3931674.post@n2.nabble.com>
In-Reply-To
<4AEEA96F.7080609@drmicha.warpmail.net>
Michael J Gruber-2 wrote:
Show 13 quoted lines
> 
> 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:
Show 6 quoted lines
> 
> 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:
Show 5 quoted lines
> 
> - 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.
Previous: Michael J GruberNext: Michael J Gruber
Message 3 of 5 in “Headless tags don't have a follows or precedes?”
  1. Tim MazidNov 1, 2009
  2. Michael J GruberNov 2, 2009
  3. Tim MazidNov 2, 2009
  4. Michael J GruberNov 2, 2009
  5. Tim MazidNov 20, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.