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

Re: git log --no-walk --tags produces strange result for certain user

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Jan 17, 2014, 08:28 UTC
Message-ID
<52D8E992.3010304@alum.mit.edu>
In-Reply-To
<52D7B4F8.1010209@alum.mit.edu>
On 01/16/2014 11:31 AM, Michael Haggerty wrote:
Show 19 quoted lines
> On 12/16/2013 12:52 PM, Kirill Likhodedov wrote:
>> I received one more complaint for this issue, and now it appears in a public repository https://github.com/spray/spray 
>>
>> To reproduce:
>>
>> # git clone https://github.com/spray/spray 
>> # cd spray
>> # git log --no-walk --tags --pretty="%H %d" --decorate=full | tail -3
>> 3273edafcd9f9701d62e061c5257c0a09e2e1fb7  (tag: refs/tags/v0.8.0-RC1)
>> ff3a2946bc54da76ddb47e82c81419cc7ae3db6b  (tag: refs/tags/v0.7.0)
>> 8b4043428b90b7f45b7241b3c2c032cf785479ce 
>>
>> So here the last hash doesn't have a decoration.
> 
> The problem is that reference refs/tags/v0.5.0 points at a tag object
> 8f6ca98087 which itself points at another tag object 2eddbcbff4 which
> finally points at commit 8b4043428b.  Probably we should handle
> recursive tag objects like this, but OTOH I can't think of a reason why
> one would want to create them in the first place.

Junio just pointed out to me that this bug has been fixed already, by Brian Carlson, in 5e1361cc, which is already in master. Sorry for the noise.

Michael
-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
Previous: Michael Haggerty
Message 11 of 11 in “git log --no-walk --tags produces strange result for certain user”
  1. Kirill LikhodedovDec 3, 2013
  2. Kirill LikhodedovDec 7, 2013
  3. Kirill LikhodedovDec 16, 2013
  4. brian m. carlsonDec 17, 2013
  5. log: properly handle decorations with chained tagsbrian m. carlson, Dec 17, 2013
  6. Junio C HamanoDec 18, 2013
  7. brian m. carlsonDec 19, 2013
  8. Junio C HamanoDec 19, 2013
  9. brian m. carlsonDec 19, 2013
  10. Michael HaggertyJan 16, 2014
  11. Michael HaggertyJan 17, 2014

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.