From: "Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Elijah Newren <newren@gmail.com>
Subject: [PATCH 1/3] git-filter-branch.txt: correct argument name typo
Date: Tue, 05 Nov 2019 23:31:30 +0000 [thread overview]
Message-ID: <5bf1b5710f7f9bc6d217e5f7c1ee0d37a6f1617f.1572996692.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.454.git.1572996692.gitgitgadget@gmail.com>
From: Elijah Newren <newren@gmail.com>
Signed-off-by: Elijah Newren <newren@gmail.com>
---
Documentation/git-filter-branch.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt
index 5876598852..1ba4667b12 100644
--- a/Documentation/git-filter-branch.txt
+++ b/Documentation/git-filter-branch.txt
@@ -649,7 +649,7 @@ create hoards of confusing empty commits
commits from before the filtering operation are also pruned instead of
just pruning commits that became empty due to filtering rules.
-* If --prune empty is specified, sometimes empty commits are missed
+* If --prune-empty is specified, sometimes empty commits are missed
and left around anyway (a somewhat rare bug, but it happens...)
* A minor issue, but users who have a goal to update all names and
--
gitgitgadget
next prev parent reply other threads:[~2019-11-05 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 23:31 [PATCH 0/3] Other doc fixes Elijah Newren via GitGitGadget
2019-11-05 23:31 ` Elijah Newren via GitGitGadget [this message]
2019-11-05 23:31 ` [PATCH 2/3] hashmap: fix documentation misuses of -> versus Elijah Newren via GitGitGadget
2019-11-05 23:31 ` [PATCH 3/3] name-hash.c: remove duplicate word in comment Elijah Newren via GitGitGadget
2019-11-07 5:41 ` Junio C Hamano
2019-11-06 4:06 ` [PATCH 0/3] Other doc fixes Jeff King
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=5bf1b5710f7f9bc6d217e5f7c1ee0d37a6f1617f.1572996692.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@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).