Thread (1 message) 1 message, 1 author, 2020-06-08

Re: [PATCH] Recommend "git gc --auto" instead of "git prune"

From: Junio C Hamano <hidden>
Date: 2020-06-08 17:34:25

Denton Liu [off-list ref] writes:
quoted
Correct.  When running manually, after noticing the need to do a GC,
it is a mental bug to add "--auto" to it, I would think.
Sorry about the confusion, when I was responding to the original
issue[0], I mistakenly typed the wrong thing. I meant to suggest
replacing it with `git gc --prune=now`, _not_ `git gc --auto` but I
guess I had my wires crossed. With this in mind...

The rationale behind this change is that John wanted to add bash
completions for `git prune`. However, I noted that prune is a plumbing
command and users should opt to use `git gc` instead. He mentioned that
sometimes when auto gc runs, it tells the user that they should run
`git prune` so I suggested (meant to suggest) replacing the command with
`git gc --prune=now` instead so that users could call the porcelain.
Nice to know.  The reasoning behind the change should be available
to those who only look at "git show".

John, if you are to send an updated patch, please make sure you have
a meaningful log message in it.

Thanks.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help