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

Fw: git describe issue

From
AEAmiel Elboim <amielel@matrix.co.il>
Date
Apr 3, 2019, 06:47 UTC
Message-ID
<AM6PR08MB4199B076CB886AE814AFF4528D570@AM6PR08MB4199.eurprd08.prod.outlook.com>
In-Reply-To
<AM6PR08MB41993844F57794DDF4B33B8F8D570@AM6PR08MB4199.eurprd08.prod.outlook.com>
Hi!
I've found strange behavior with 'git describe' command, look like for me as bug. 
In the case I create 2 tags on same commit and I run 'git describe --tags' I expect to get the latest tag, but always I get the first tag I created on the commit.
Unlike git-describe documentations - "The command finds the most recent tag that is reachable from a commit. "
Simple example -   
amiel@CLINIKALDEV10:~/Xpress$ git tag v1
amiel@CLINIKALDEV10:~/Xpress$ git tag v2
amiel@CLINIKALDEV10:~/Xpress$ git describe --tags
v1
amiel@CLINIKALDEV10:~/Xpress$ gl
* 4f54749 (HEAD -> master, tag: v2, tag: v1, origin/master, origin/HEAD) start point with git
I'll happy to know if is bug or I don't understand something.
Thanks
Amiel  
  
     
Next: Bryan Turner
Message 1 of 4 in “Fw: git describe issue”
  1. Amiel ElboimApr 3, 2019
  2. Bryan TurnerApr 3, 2019
  3. Bryan TurnerApr 3, 2019
  4. Philip OakleyApr 3, 2019

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.