Re: [PATCH] doc/git-branch: fix --force description typo

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 27, 2022, 04:46 UTC
Message-ID: <xmqqcz85v4h4.fsf@gitster.g>
In-Reply-To: <20221226165441.126625-1-kyle@kyleam.com>

Kyle Meyer <kyle@kyleam.com> writes:

> Subject: Re: [PATCH] doc/git-branch: fix --force description typo

> Update the description of --force to use '<start-point>' rather than
> '<startpoint>' to match the spelling used everywhere else in the
> git-branch documentation.

Thanks. This <startpoint> was written in 2017, and all other lines that say "start-point", except for one, blame on commits made in 2019-2022, but they have been inherited from older versions.

Apparently we missed to convert this single one for consistency.

Good find.  Will queue.  Thanks.

Show 18 quoted lines

> Signed-off-by: Kyle Meyer <kyle@kyleam.com>
> ---
>  Documentation/git-branch.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt
> index 12c5f84e3b..aa2f78c4c2 100644
> --- a/Documentation/git-branch.txt
> +++ b/Documentation/git-branch.txt
> @@ -116,7 +116,7 @@ OPTIONS
>  
>  -f::
>  --force::
> -	Reset <branchname> to <startpoint>, even if <branchname> exists
> +	Reset <branchname> to <start-point>, even if <branchname> exists
>  	already. Without `-f`, 'git branch' refuses to change an existing branch.
>  	In combination with `-d` (or `--delete`), allow deleting the
>  	branch irrespective of its merged status, or whether it even