git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Beshr Kayali <me@beshr.com>, git@vger.kernel.org
Subject: Re: [PATCH 1/1] Documentation: commit patch typo
Date: Mon, 28 Jun 2021 13:05:17 +0700	[thread overview]
Message-ID: <afef1ee8-dd6e-2954-2c97-57ae14b27668@gmail.com> (raw)
In-Reply-To: <20210628052631.345601-2-me@beshr.com>

Hi Beshr, welcome to Git mailing list!

On 28/06/21 12.26, Beshr Kayali wrote:
> ---
>   Documentation/git-commit.txt | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
Why isn't there commit message? But from cover letter of this 
single-patch series:

> Simple typo fix (chose -> choose) in the documentation of the patch option under the commit command.

Don't forget to write the commit message in next series.

> diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt
> index 340c5fbb48..95fec5f069 100644
> --- a/Documentation/git-commit.txt
> +++ b/Documentation/git-commit.txt
> @@ -72,7 +72,7 @@ OPTIONS
>   
>   -p::
>   --patch::
> -	Use the interactive patch selection interface to chose
> +	Use the interactive patch selection interface to choose
>   	which changes to commit. See linkgit:git-add[1] for
>   	details.

Fix looks OK.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

  reply	other threads:[~2021-06-28  6:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28  5:26 [PATCH 0/1] fix a typo in patch option of the commit command Beshr Kayali
2021-06-28  5:26 ` [PATCH 1/1] Documentation: commit patch typo Beshr Kayali
2021-06-28  6:05   ` Bagas Sanjaya [this message]
2021-06-28 19:12     ` Beshr Kayali
2021-06-28 19:37 ` [PATCH v2 0/1] Documentation: Fix typo in patch option of the commit command Beshr Kayali
2021-06-28 19:37   ` [PATCH v2 1/1] " Beshr Kayali

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=afef1ee8-dd6e-2954-2c97-57ae14b27668@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=me@beshr.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).