All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] doc/git-branch: fix --force description typo
Date: Tue, 27 Dec 2022 13:46:15 +0900	[thread overview]
Message-ID: <xmqqcz85v4h4.fsf@gitster.g> (raw)
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.

> 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

      reply	other threads:[~2022-12-27  4:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26 16:54 [PATCH] doc/git-branch: fix --force description typo Kyle Meyer
2022-12-27  4:46 ` Junio C Hamano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqcz85v4h4.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=kyle@kyleam.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.