From: "John Lin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: John Lin <johnlinp@gmail.com>, John Lin <johnlinp@gmail.com>
Subject: [PATCH] Recommend "git gc --prune=now" instead of "git prune"
Date: Mon, 08 Jun 2020 02:02:18 +0000 [thread overview]
Message-ID: <pull.652.git.1591581739031.gitgitgadget@gmail.com> (raw)
From: John Lin <johnlinp@gmail.com>
Signed-off-by: John Lin <johnlinp@gmail.com>
---
Recommend "git gc --prune=now" instead of "git prune"
Signed-off-by: John Lin johnlinp@gmail.com [johnlinp@gmail.com]
Fix according to #642.
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-652%2Fjohnlinp%2Ffix-git-gc-warning-message-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-652/johnlinp/fix-git-gc-warning-message-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/652
builtin/gc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/gc.c b/builtin/gc.c
index 8e0b9cf41b3..74185eac917 100644
--- a/builtin/gc.c
+++ b/builtin/gc.c
@@ -692,7 +692,7 @@ int cmd_gc(int argc, const char **argv, const char *prefix)
if (auto_gc && too_many_loose_objects())
warning(_("There are too many unreachable loose objects; "
- "run 'git prune' to remove them."));
+ "run 'git gc --prune=now' to remove them."));
if (!daemonized)
unlink(git_path("gc.log"));
base-commit: 20514004ddf1a3528de8933bc32f284e175e1012
--
gitgitgadget
next reply other threads:[~2020-06-08 2:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 2:02 John Lin via GitGitGadget [this message]
2020-06-08 10:17 ` [PATCH] Recommend "git gc --prune=now" instead of "git prune" 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
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=pull.652.git.1591581739031.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--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).