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

Re: [PATCH 0/2] builtin/receive-pack: convert to use git-maintenance(1)

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 17, 2024, 16:53 UTC
Message-ID
<xmqqwmow7wwp.fsf@gitster.g>
In-Reply-To
<CAOLa=ZTRY6hmQqC2BozFkLmLQWnkQ4+sSug_8N1ZY9+aHNqCTg@mail.gmail.com>
Karthik Nayak <karthik.188@gmail.com> writes:
Show 6 quoted lines
>> this small patch series adapts git-receive-pack(1) to spawn `git
>> maintenance run --auto` instead of `git gc --auto` like all the other
>> parts of our codebase do nowadays. This removes the last internal user
>> of `git gc --auto`.
>
> I don't have enough context here, so why do this?

I think the intent of a95ce124 (maintenance: replace run_auto_gc(), 2020-09-17) was to update all codepaths that run "git gc --auto" to instead run "git maintenance --auto", but only updated the ones that used to call run_auto_gc(). The codepath Patrick found runs "git gc --auto" without using run_auto_gc() and was left behind when the others were converted.

So why do this? I think "To follow through a95ce124 started" would probably be a good enough reason, if a reader is on board with what a95ce124 wanted to do.

Do we have a handy reference that compares "gc --auto" and "maintenance --auto"? Are they essentially the same thing these days? What are the things that is done by one but not by the other?

THanks.
Previous: Karthik NayakNext: Patrick Steinhardt
Message 8 of 9 in “builtin/receive-pack: convert to use git-maintenance(1)”
  1. 0/2 builtin/receive-pack: convert to use git-maintenance(1)Patrick Steinhardt, Apr 17, 2024
  2. 1/2 run-command: introduce function to prepare auto-maintenance processPatrick Steinhardt, Apr 17, 2024
  3. Junio C HamanoApr 17, 2024
  4. Patrick SteinhardtApr 18, 2024
  5. 2/2 builtin/receive-pack: convert to use git-maintenance(1)Patrick Steinhardt, Apr 17, 2024
  6. Karthik NayakApr 17, 2024
  7. Karthik NayakApr 17, 2024
  8. Junio C HamanoApr 17, 2024
  9. Patrick SteinhardtApr 18, 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.