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

Re: git describe weird behaviour

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Nov 10, 2010, 21:24 UTC
Message-ID
<20101110212410.GA13782@burratino>
In-Reply-To
<20101110204034.GO22105@genesis.frugalware.org>
Miklos Vajna wrote:
> But I think the approach to follow the first parent only would solve the
> problem outlined in the commit message of 80dbae0 as well: I think it's
> pretty rare to tag a commit in a feature branch, then merge it.

Doesn't that happen in linux-2.6 history fairly often (subsystem trees syncing with upstream)?

Previous: Miklos VajnaNext: Miklos Vajna
Message 10 of 11 in “git describe weird behaviour”
  1. Miklos VajnaNov 10, 2010
  2. Jeff KingNov 10, 2010
  3. MaaartinNov 10, 2010
  4. Thomas RastNov 10, 2010
  5. Miklos VajnaNov 10, 2010
  6. Miklos VajnaDec 9, 2010
  7. Jeff KingDec 9, 2010
  8. Junio C HamanoNov 10, 2010
  9. Miklos VajnaNov 10, 2010
  10. Jonathan NiederNov 10, 2010
  11. Miklos VajnaNov 10, 2010

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.