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

Re: Current Issues #3

From
Daniel Barkalow <barkalow@iabervon.org>
Date
May 22, 2006, 21:54 UTC
Message-ID
<Pine.LNX.4.64.0605221738090.6713@iabervon.org>
In-Reply-To
<7v8xoue9eo.fsf@assigned-by-dhcp.cox.net>
On Mon, 22 May 2006, Junio C Hamano wrote:
Show 7 quoted lines
> * reflog
> 
>   I still haven't merged this series to "next" -- I do not have
>   much against what the code does, but I am unconvinced if it is
>   useful.  Also objections raised on the list that this can be
>   replaced by making sure that a repository that has hundreds of
>   tags usable certainly have a point.

I think it would make gitweb's summary view clearer, and Linus seemed interested in being able to look up what happened in the fast forward which was the first of several merges in a day.

It could be replaced by a repository with hundreds of machine-readable tags with code to parse dates into queries for suitable tags. But I don't think there's an advantage to using the tag mechanism here, because you never want to look the history up by exactly which history it is (the thing that a tag ref is good for); you'll be looking for whatever reflog item is the newest not after a specified time, where the specified time is almost never a time that a reflog item was created.

	-Daniel
*This .sig left intentionally blank*
Previous: Martin WaitzNext: Carl Worth
Message 6 of 8 in “Current Issues #3”
  1. Junio C HamanoMay 22, 2006
  2. Linus TorvaldsMay 22, 2006
  3. SeanMay 22, 2006
  4. Jakub NarebskiMay 23, 2006
  5. Martin WaitzMay 22, 2006
  6. Daniel BarkalowMay 22, 2006
  7. Carl WorthMay 22, 2006
  8. Shawn PearceMay 22, 2006

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.