Re: git and time

From: Linus Torvalds <torvalds@osdl.org>
Date: Oct 1, 2006, 00:13 UTC
Message-ID: <Pine.LNX.4.64.0609301712340.3952@g5.osdl.org>
In-Reply-To: <7vd59d7y8v.fsf@assigned-by-dhcp.cox.net>

On Sat, 30 Sep 2006, Junio C Hamano wrote:

Show 10 quoted lines

> 
> However, I think the traditional "find the closest ancestor"
> behaviour and ref-log behaviour are mutually incompatible, while
> they both return information to help address similar issues to
> the end user when viewed at a very high level.
> 
> Especially, "find the closest ancestor" behaviour means when you
> get "tag-gXXXX" as an answer, the tag proper does _not_ contain
> the given commit (e.g. commit v1.4.2-g4839bd8 is not part of
> v1.4.2).

Correct.

But that just means that we should take the _next_ one in the time-ordered list, no?

		Linus

$ 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.