git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "lgl via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, lgl <liginity@outlook.com>
Subject: Re: [PATCH] fix typo in git-mktree.txt
Date: Wed, 02 Feb 2022 10:32:21 -0800	[thread overview]
Message-ID: <xmqqfsp115my.fsf@gitster.g> (raw)
In-Reply-To: <pull.1207.git.git.1643792450866.gitgitgadget@gmail.com> (lgl via GitGitGadget's message of "Wed, 02 Feb 2022 09:00:50 +0000")

"lgl via GitGitGadget" <gitgitgadget@gmail.com> writes:

> From: liginity <liginity@outlook.com>
>
> fix a typo: change "as" to "a".
>  --batch::
>  	Allow building of more than one tree object before exiting.  Each
> -	tree is separated by as single blank line. The final new-line is
> +	tree is separated by a single blank line. The final new-line is

Makes sense; will queue.

Thanks.

  parent reply	other threads:[~2022-02-02 18:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02  9:00 [PATCH] fix typo in git-mktree.txt lgl via GitGitGadget
2022-02-02  9:33 ` Ævar Arnfjörð Bjarmason
2022-02-02 18:32 ` Junio C Hamano [this message]
2022-02-02 18:46   ` Junio C Hamano

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=xmqqfsp115my.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=liginity@outlook.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 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 NNTP newsgroup(s).