From: Junio C Hamano <gitster@pobox•com>
To: Roberto Tyley <roberto.tyley@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: [PATCH 2/2] Add submitGit patch-submission information
Date: Thu, 14 Apr 2016 16:03:51 -0700 [thread overview]
Message-ID: <xmqqpotreqso.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqq37qng721.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Thu, 14 Apr 2016 15:27:18 -0700")
Junio C Hamano <gitster@pobox•com> writes:
>> +Because of these factors, it's recommended that you use one of these
>> +specific methods to generate and send your patchs:
>
> Perhaps:
>
> It's recommended ... your patches, unless you already know how
> to correctly send your patches as plain-text e-mails.
>
> That is, the ones listed below are known to produce good patches,
> but our recommendation is _so_ strong to urge users with working
Well, I meant "our recommendation is *not* so strong" here.
next prev parent reply other threads:[~2016-04-14 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 22:12 [PATCH 1/2] Partition SubmittingPatches doc into two files Roberto Tyley
2016-04-14 22:12 ` [PATCH 2/2] Add submitGit patch-submission information Roberto Tyley
2016-04-14 22:27 ` Junio C Hamano
2016-04-14 23:03 ` Junio C Hamano [this message]
2016-04-15 2:05 ` Jeff King
2016-04-14 22:16 ` [PATCH 1/2] Partition SubmittingPatches doc into two files 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=xmqqpotreqso.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=roberto.tyley@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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