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

Re: Git Bug Report: out of memory using git tag

From
Taylor Blau <me@ttaylorr.com>
Date
Nov 3, 2022, 00:42 UTC
Message-ID
<Y2MOYfalWOB9YlP2@nand.local>
In-Reply-To
<Y2IeqOT5Ao1Qa0Zl@coredump.intra.peff.net>
On Wed, Nov 02, 2022 at 03:39:20AM -0400, Jeff King wrote:
Show 9 quoted lines
> After sleeping on it, I think I fully understand what's going on. There
> are actually _two_ bugs, but they are closely related. ;)
>
> Here are patches which fix them both. I may be setting a new record for
> the ratio of commit message lines to changed code. But it took me a
> while to figure out what was going on, so I wanted to explain it fully.
>
>   [1/2]: ref-filter: fix parsing of signatures without blank lines
>   [2/2]: ref-filter: fix parsing of signatures with CRLF and no body

Indeed. I agree with others below in the thread that this is very well explained, and the fix(es) both look sensible to me.

Will queue, thanks.

Thanks, Taylor

Previous: Jeff KingNext: Philippe Blain
Message 14 of 15 in “Git Bug Report: out of memory using git tag”
  1. Martin EnglundOct 28, 2022
  2. Jeff KingNov 1, 2022
  3. Philippe BlainNov 2, 2022
  4. Jeff KingNov 2, 2022
  5. 1/2 ref-filter: fix parsing of signatures without blank linesJeff King, Nov 2, 2022
  6. 2/2 ref-filter: fix parsing of signatures with CRLF and no bodyJeff King, Nov 2, 2022
  7. Elijah NewrenNov 2, 2022
  8. gigantic commit messages, was Re: Git Bug Report: out of memory using git tagJeff King, Nov 2, 2022
  9. Ævar Arnfjörð BjarmasonNov 2, 2022
  10. Elijah NewrenNov 2, 2022
  11. Eric SunshineNov 2, 2022
  12. Philippe BlainNov 2, 2022
  13. Jeff KingNov 3, 2022
  14. Taylor BlauNov 3, 2022
  15. Philippe BlainNov 2, 2022

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.