From: Rubén Justo <rjusto@gmail.com>
Date: Sat, 6 Jan 2024 14:38:37 +0000 (+0100)
Subject: branch: clarify <oldbranch> term
X-Git-Tag: v2.44.0-rc0~70^2
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=5aea3955bcd716c5dcb3323ef4eab72da70db623;p=thirdparty%2Fgit.git

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>
---

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