From: Junio C Hamano <gitster@pobox.com>
To: "John Lin via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, John Lin <johnlinp@gmail.com>
Subject: Re: [PATCH v2] gc: recommend `git gc --prune=now` instead of `git prune`
Date: Mon, 08 Jun 2020 22:07:36 -0700 [thread overview]
Message-ID: <xmqqv9k0j087.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <pull.652.v2.git.1591662224566.gitgitgadget@gmail.com> (John Lin via GitGitGadget's message of "Tue, 09 Jun 2020 00:23:44 +0000")
"John Lin via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: John Lin <johnlinp@gmail.com>
>
> `git prune` is a plumbing command and should not be run directly by
> users. The corresponding porcelain command is `git gc`, which is
> mentioned in the man page of `git prune`.
Much better than v1 that came without any justification ;-)
I however wouldn't say "should not"---that feels a bit too strong (I
personally use "prune" from the command line once or twice every
week and do not see why I should be forbidden from doing so [*1*]),
but the users who see this message would not need such a precise
control afforded by use of "git prune", so "gc --prune=now" is a
better recommendation.
Thanks.
[Footnote]
*1* The command does not even produce a machine readable output.
The reason it is not recommended (but that is different from
"should not") to casual users over "git gc" is because it is a
very focused tool (it is only about removing loose objects and
does not touch other things) and applicable to a very specific
condition. Those who can recognize that they are in that
situation should not be forbidden from using it with a dogmatic
"should not".
next prev parent reply other threads:[~2020-06-09 5:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 2:02 [PATCH] Recommend "git gc --prune=now" instead of "git prune" John Lin via GitGitGadget
2020-06-08 10:17 ` Denton Liu
2020-06-09 0:23 ` [PATCH v2] gc: recommend `git gc --prune=now` instead of `git prune` John Lin via GitGitGadget
2020-06-09 5:07 ` Junio C Hamano [this message]
2020-06-09 11:06 ` Ævar Arnfjörð Bjarmason
2020-06-09 16:03 ` Junio C Hamano
2020-06-10 3:43 ` 林自均
2020-06-10 3:47 ` Denton Liu
2020-06-10 7:38 ` 林自均
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqv9k0j087.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=johnlinp@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).