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

Re: [PATCH v3] Fix to avoid high memory footprint

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 26, 2024, 15:12 UTC
Message-ID
<xmqqa5i4yypc.fsf@gitster.g>
In-Reply-To
<pull.1744.v3.git.git.1721975234873.gitgitgadget@gmail.com>
"Haritha  via GitGitGadget" <gitgitgadget@gmail.com> writes:
Another thing.
> Subject: Re: [PATCH v3] Fix to avoid high memory footprint

This does not tell us much about what area had problem under what condition. "git shortlog --no-merges -200 master" may give us good examples of how we typically write the title of our commits.

In the case of this change, ideally we should be able to tell that this is about tracing the conversion codepath.

    Subject: [PATCH vN] encoding: return early when not tracing conversion
or something, perhaps?
Previous: Junio C HamanoNext: Haritha D
Message 14 of 15 in “Fix to avoid high memory footprint”
  1. Fix to avoid high memory footprintHaritha via GitGitGadget, Jul 16, 2024
  2. Jeff KingJul 17, 2024
  3. Fix to avoid high memory footprintHaritha via GitGitGadget, Jul 24, 2024
  4. Junio C HamanoJul 24, 2024
  5. Jeff KingJul 24, 2024
  6. Fix to avoid high memory footprintHaritha via GitGitGadget, Jul 26, 2024
  7. Torsten BögershausenJul 26, 2024
  8. convert: avoid high memory footprintHaritha via GitGitGadget, Jul 26, 2024
  9. convert: return early when not tracingHaritha via GitGitGadget, Jul 30, 2024
  10. Junio C HamanoJul 31, 2024
  11. Haritha DJul 31, 2024
  12. convert: return early when not tracingHaritha via GitGitGadget, Jul 31, 2024
  13. Junio C HamanoJul 26, 2024
  14. Junio C HamanoJul 26, 2024
  15. Haritha DJul 30, 2024

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.