summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRubén Justo <rjusto@gmail.com>2024-01-06 15:38:37 +0100
committerJunio C Hamano <gitster@pobox.com>2024-01-08 19:06:05 +0100
commit5aea3955bcd716c5dcb3323ef4eab72da70db623 (patch)
tree74236ad6f22d80db0dc7638f20b2b27bc209b7e5
parentGit 2.43 (diff)
downloadgit-5aea3955bcd716c5dcb3323ef4eab72da70db623.tar.xz
git-5aea3955bcd716c5dcb3323ef4eab72da70db623.zip
branch: clarify <oldbranch> term
Since 52d59cc645 (branch: add a --copy (-c) option to go with --move (-m), 2017-06-18) <oldbranch> is used in more operations than just -m. Let's also clarify what we do if <oldbranch> is omitted. Signed-off-by: Rubén Justo <rjusto@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/git-branch.txt3
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt
index 4395aa9354..0b08442932 100644
--- a/Documentation/git-branch.txt
+++ b/Documentation/git-branch.txt
@@ -312,7 +312,8 @@ superproject's "origin/main", but tracks the submodule's "origin/main".
option is omitted, the current HEAD will be used instead.
<oldbranch>::
- The name of an existing branch to rename.
+ The name of an existing branch. If this option is omitted,
+ the name of the current branch will be used instead.
<newbranch>::
The new name for an existing branch. The same restrictions as for