From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Hillf Danton <dhillf@gmail.com>
Cc: trivial@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC V2]remove extra semicolons from various parts of the kernel
Date: Wed, 27 Jul 2011 08:04:12 -0700 [thread overview]
Message-ID: <4E3028EC.1010200@gmail.com> (raw)
In-Reply-To: <CAJd=RBB4=VH=2Z2H3BP+2cvf8KmpbnkVuWyFdK24pp94gZwu9Q@mail.gmail.com>
On 07/27/2011 05:01 AM, Hillf Danton wrote:
> On Wed, Jul 27, 2011 at 2:06 PM, Justin P. Mattock
> <justinmattock@gmail.com> wrote:
>> From: "Justin P. Mattock"<justinmattock@gmail.com>
>>
>> This is a resend from the original, changing the title from PATCH to
>> RFC(since this is a review for commit, and I should have put that the first go around).
>> and also removing some of the commit's with ia64 and bash since it is significant.
>> let me know if I might have missed anything etc..
>>
>> Signed-off-by: Justin P. Mattock<justinmattock@gmail.com>
>>
> Acked-by: Hillf Danton<dhillf@gmail.com>
>
> btw, would you please, Justin, share howto tame gmail not to malform the patch
> produced by git diff, say wrap lines with more than 80-char, or howto
> config git?
>
Cool Thanks!
all I do is use git send email to send out the patches(seems to not
mangle things). As for tweaking any of the clients to work properly or
even gmail itself, I would not really know what todo(need to do my
homework with that). All info is under: Documentation/email-clients.txt
hope it helps.
Justin P. Mattock
next prev parent reply other threads:[~2011-07-27 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 6:06 [RFC V2]remove extra semicolons from various parts of the kernel Justin P. Mattock
2011-07-27 12:01 ` Hillf Danton
2011-07-27 15:04 ` Justin P. Mattock [this message]
2011-07-30 17:27 ` Fubo Chen
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=4E3028EC.1010200@gmail.com \
--to=justinmattock@gmail.com \
--cc=dhillf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
/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