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

Re: [RFC 0/1] Tolerate broken headers in `packed-refs` files

From
Jeff King <peff@peff.net>
Date
Mar 26, 2018, 14:33 UTC
Message-ID
<20180326143340.GA23926@sigill.intra.peff.net>
In-Reply-To
<f8d0f3b6-69b3-ba42-c39c-551814caf335@gmail.com>
On Mon, Mar 26, 2018 at 09:08:04AM -0400, Derrick Stolee wrote:
> Since most heavily-used tools that didn't spawn Git processes use LibGit2 to
> interact with Git repos, I added Ed Thomson to CC to see if libgit2 could
> ever write these bad header comments.

Ed can probably answer more definitively, but I dug in the libgit2 history a little, and I think it has only ever generated correct "pack-refs with:" lines.

Ditto for JGit, though there it blames down to 1a6964c82 (Initial JGit contribution to eclipse.org, 2009-09-29). I didn't dig further into the historical JGit repository, but I think that's probably far enough to feel good about it.

-Peff
Previous: Derrick StoleeNext: Edward Thomson
Message 4 of 5 in “[RFC 0/1] Tolerate broken headers in `packed-refs` files”
  1. Michael HaggertyMar 26, 2018
  2. 1/1 packed-backend: ignore broken headersMichael Haggerty, Mar 26, 2018
  3. Derrick StoleeMar 26, 2018
  4. Jeff KingMar 26, 2018
  5. Edward ThomsonMar 26, 2018

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.