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 --auto" instead of "git prune"
Date: Sun, 07 Jun 2020 16:18:35 +0000 [thread overview]
Message-ID: <pull.651.git.1591546715913.gitgitgadget@gmail.com> (raw)
From: John Lin <johnlinp@gmail.com>
Signed-off-by: John Lin <johnlinp@gmail.com>
---
Recommend "git gc --auto" instead of "git prune"
Fix according to #642.
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-651%2Fjohnlinp%2Ffix-git-gc-warning-message-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-651/johnlinp/fix-git-gc-warning-message-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/651
builtin/gc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/gc.c b/builtin/gc.c
index 8e0b9cf41b3..3833a3de332 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 --auto' to remove them."));
if (!daemonized)
unlink(git_path("gc.log"));
base-commit: 20514004ddf1a3528de8933bc32f284e175e1012
--
gitgitgadget
next reply other threads:[~2020-06-07 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 16:18 John Lin via GitGitGadget [this message]
2020-06-07 16:25 ` [PATCH] Recommend "git gc --auto" instead of "git prune" brian m. carlson
2020-06-07 17:10 ` Junio C Hamano
2020-06-07 20:45 ` Denton Liu
2020-06-08 17:34 ` Junio C Hamano
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.651.git.1591546715913.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.