From: Stefan Beller <stefanbeller@googlemail.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: rob@landley.net, jgarzik@pobox.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND][PATCH] Rewrite Documentation/SubmittingPatches.
Date: Mon, 23 Jul 2012 09:20:57 +0200 [thread overview]
Message-ID: <500CFB59.6040305@googlemail.com> (raw)
In-Reply-To: <500CD6CC.2000108@xenotime.net>
On 07/23/2012 06:45 AM, Randy Dunlap wrote:
> On 07/22/2012 12:56 AM, Stefan Beller wrote:
>
>> Documentation/SubmittingPatches | 191 ++++++++++++++++++++++++----------------
>> 1 file changed, 116 insertions(+), 75 deletions(-)
>>
>> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
>> index c379a2a..ac00451 100644
>> --- a/Documentation/SubmittingPatches
>> +++ b/Documentation/SubmittingPatches
>> @@ -163,9 +157,9 @@ Do not send more than 15 patches at once to the vger mailing lists!!!
>> Linus Torvalds is the final arbiter of all changes accepted into the
>> -Linux kernel. His e-mail address is <torvalds@linux-foundation.org>.
>> +Linux kernel. His e-mail address is <torvalds@linux-foundation.org>.
>
> what are the changes on the line above and below, please?
>
>> He gets a lot of e-mail, so typically you should do your best to -avoid-
>> -sending him e-mail.
>> +sending him e-mail.
>
>
>
> thanks,
>
There used to be a whitespace after each of both lines, but my mailprogram removed them, so in
the actually sent patch they seem to be equal. :/
next prev parent reply other threads:[~2012-07-23 7:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <500BAFE0.8070108@googlemail.com>
2012-07-22 7:56 ` [RESEND][PATCH] Rewrite Documentation/SubmittingPatches Stefan Beller
2012-07-23 4:45 ` Randy Dunlap
2012-07-23 7:20 ` Stefan Beller [this message]
2012-07-23 15:29 ` Randy Dunlap
2012-11-23 9:49 ` Stefan Beller
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=500CFB59.6040305@googlemail.com \
--to=stefanbeller@googlemail.com \
--cc=jgarzik@pobox.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=rob@landley.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