[PATCH] branch: clarify <oldbranch> and <newbranch> terms further
- From
- Dragan Simic <dsimic@manjaro.org>
- Date
- Feb 5, 2024, 12:45 UTC
- Message-ID
- <e2eb777bca8ffeec42bdd684837d28dd52cfc9c3.1707136999.git.dsimic@manjaro.org>
Clarify further the uses for <oldbranch> and describe the additional use for <newbranch>. Mentioning both renaming and copying in these places might seem a bit redundant, but it should actually make understanding these terms easier to the readers of the git-branch(1) man page.
Signed-off-by: Dragan Simic <dsimic@manjaro.org> --- Documentation/git-branch.txt | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt index 0b0844293235..7392c2f0797d 100644 --- a/Documentation/git-branch.txt +++ b/Documentation/git-branch.txt @@ -312,12 +312,14 @@ 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. If this option is omitted, - the name of the current branch will be used instead. + The name of an existing branch to be renamed or copied. + 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 - <branchname> apply. + The new name for an existing branch, when renaming a branch, + or the name for a new branch, when copying a branch. The same + naming restrictions apply as for <branchname>. --sort=<key>:: Sort based on the key given. Prefix `-` to sort in descending