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

Re: Regarding: git-lost+found

From
Junio C Hamano <junkio@cox.net>
Date
Nov 9, 2005, 23:23 UTC
Message-ID
<7vwtjh8kxu.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.64.0511091759520.25300@iabervon.org>
Daniel Barkalow <barkalow@iabervon.org> writes:
> Why have git-lost+found write to files at all? It seems to me easiest to 
> have the list go to standard out, and you could do "gitk `git-lost+found 
> -t commit`" to see lost commits, and reconnect them as desired. (Making up 
> command line syntax for listing only the commits.)

That is certainly cleaner. The only downside is fsck-objects that lost+found uses tends to be expensive operation, and what you would want to do with the information may be more than just use it on the command line of gitk. But in any case the user could store git-lost+found output in a file to do whatever she wants, so it may not matter.

Previous: Daniel BarkalowNext: Daniel Barkalow
Message 6 of 9 in “Regarding: git-lost+found”
  1. Johannes SchindelinNov 8, 2005
  2. Petr BaudisNov 8, 2005
  3. Petr BaudisNov 8, 2005
  4. Junio C HamanoNov 9, 2005
  5. Daniel BarkalowNov 9, 2005
  6. Junio C HamanoNov 9, 2005
  7. Daniel BarkalowNov 10, 2005
  8. Matthias UrlichsNov 14, 2005
  9. Fix git-rev-list "date order" with --topo-orderLinus Torvalds, Nov 14, 2005

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.