Skip to content

Commit e61cb19

Browse files
committed
branch doc: sprinkle a few commas for readability
The "--force" option can also be used when the named branch does not yet exist, and the point of the option is the user can (re)point the branch to the named commit even if it does. Add 'even' before 'if' to clarify. Also, insert another comma after "Without -f" before "the command refuses..." to make the text easier to parse. Incidentally, this change should help certain versions of docbook-xsl-stylesheets that render the original without any whitespace between "-f" and "git". Noticed-by: Lars Schneider <[email protected]> Helped-by: Jeff King <[email protected]> Helped-by: Andreas Schwab <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 4010f1d commit e61cb19

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Documentation/git-branch.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -99,8 +99,8 @@ OPTIONS
9999

100100
-f::
101101
--force::
102-
Reset <branchname> to <startpoint> if <branchname> exists
103-
already. Without `-f` 'git branch' refuses to change an existing branch.
102+
Reset <branchname> to <startpoint>, even if <branchname> exists
103+
already. Without `-f`, 'git branch' refuses to change an existing branch.
104104
In combination with `-d` (or `--delete`), allow deleting the
105105
branch irrespective of its merged status. In combination with
106106
`-m` (or `--move`), allow renaming the branch even if the new

0 commit comments

Comments
 (0)