From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Wesley Schwengle <wesleys@opperschaap.net>, git@vger.kernel.org
Subject: Re: [PATCH] Fix grammar in git push man page
Date: Thu, 10 Aug 2023 08:45:29 +0700 [thread overview]
Message-ID: <f6ef3689-820a-f85c-68a7-9c87a5eabe27@gmail.com> (raw)
In-Reply-To: <ZNRANBdZG9kAnjxq@debian.me>
On 10/08/2023 08:41, Bagas Sanjaya wrote:
> On Wed, Aug 09, 2023 at 08:40:25PM -0400, Wesley Schwengle wrote:
>> -When neither the command-line nor the configuration specify what to
>> +When neither the command line nor the configuration specifies what to
>
> IMO either command-line or command line is correct...
>
Oops, I mean both forms (with and without dash) are correct.
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2023-08-10 1:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 0:40 [PATCH] Fix grammar in git push man page Wesley Schwengle
2023-08-10 1:13 ` Junio C Hamano
2023-08-10 1:21 ` [[PATCH v2]] git-push.txt: fix grammar Wesley Schwengle
2023-08-10 1:41 ` [PATCH] Fix grammar in git push man page Bagas Sanjaya
2023-08-10 1:45 ` Bagas Sanjaya [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=f6ef3689-820a-f85c-68a7-9c87a5eabe27@gmail.com \
--to=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=wesleys@opperschaap.net \
/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).