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

Re: is it "git gc --prune=now" or "git gc --prune=all"?

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 11, 2019, 02:18 UTC
Message-ID
<xmqqsgvukvc6.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<alpine.LFD.2.21.1903091309130.16641@localhost.localdomain>
"Robert P. J. Day" <rpjday@crashcourse.ca> writes:
Show 13 quoted lines
> On Wed, 6 Mar 2019, Junio C Hamano wrote:
>
>> Jeff King <peff@peff.net> writes:
>>
>> > ... I do think the documentation should recommend "now". Possibly
>> > builtin/gc.c should be smarter about recognizing "all" in the
>> > conditional you quoted, too, though I don't know that it's all
>> > that important (especially if we tweak the documentation).
>>
>> Yup, as the placeholder for the value is labeled as "<date>", "now"
>> would be the one we should be encouraging.
>
>   i can submit an obviously trivial patch for that

You already did to turn --prune=all into --prune=now in the doc, I think.

Do we encourage 'false' where we should encourage 'never'? I see we do not even mention the negative form in git-gc manpage, and I think it is a good thing, especially because --prune=<date> is listed just next to --no-prune, which is even more explicit.

Previous: Robert P. J. Day
Message 5 of 5 in “is it "git gc --prune=now" or "git gc --prune=all"?”
  1. Robert P. J. DayMar 2, 2019
  2. Jeff KingMar 5, 2019
  3. Junio C HamanoMar 6, 2019
  4. Robert P. J. DayMar 9, 2019
  5. Junio C HamanoMar 11, 2019

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.