summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2021-02-03 16:07:32 -0500
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-02-03 14:14:31 -0800
commit27dc071b9a11e953ea7d73bfdf6103940d039215 (patch)
tree90416afba3908b56b3b0b5af3643a62e282c2440
parentcompletion: handle other variants of "branch -m" (diff)
downloadtgif-27dc071b9a11e953ea7d73bfdf6103940d039215.tar.xz
doc/git-branch: fix awkward wording for "-c"
The description for "-c" is hard to parse. I think the big issue is lack of commas, but I've also reordered the words to keep the main focus point of "instead of renaming, copy" together. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/git-branch.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt
index adaa1782a8..eb815c2248 100644
--- a/Documentation/git-branch.txt
+++ b/Documentation/git-branch.txt
@@ -78,8 +78,8 @@ renaming. If <newbranch> exists, -M must be used to force the rename
to happen.
The `-c` and `-C` options have the exact same semantics as `-m` and
-`-M`, except instead of the branch being renamed it along with its
-config and reflog will be copied to a new name.
+`-M`, except instead of the branch being renamed, it will be copied to a
+new name, along with its config and reflog.
With a `-d` or `-D` option, `<branchname>` will be deleted. You may
specify more than one branch for deletion. If the branch currently