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

Re: How to (re-)create .git/logs/refs

From
HSHolger Schurig <hs4233@mail.mn-solutions.de>
Date
May 13, 2008, 09:11 UTC
Message-ID
<200805131111.42517.hs4233@mail.mn-solutions.de>
In-Reply-To
<200805130842.06112.hs4233@mail.mn-solutions.de>
> Okay, then I presume it's a shortcoming that the @{date}
> syntax uses .git/logs/ref.

Is there any reason sha1_name.c (which is responsible for the @{} syntax) doesn't include list-objects.h and uses traverse_commit_list() for it's purposes? It wouldn't then need to use .git/logs/ref anymore.

If that would be ok, then maybe I find time (in my spare time) and prepare a patch in this direction.

Previous: Holger SchurigNext: Andreas Ericsson
Message 5 of 10 in “How to (re-)create .git/logs/refs”
  1. Holger SchurigMay 8, 2008
  2. Holger SchurigMay 8, 2008
  3. Nicolas PitreMay 8, 2008
  4. Holger SchurigMay 13, 2008
  5. Holger SchurigMay 13, 2008
  6. Andreas EricssonMay 13, 2008
  7. Johannes SchindelinMay 13, 2008
  8. Holger SchurigMay 13, 2008
  9. Jakub NarebskiMay 13, 2008
  10. Holger SchurigMay 13, 2008

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.