From: Peter Foley <pefoley2@verizon.net>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: <linux-kernel@vger.kernel.org>, <linux-kbuild@vger.kernel.org>,
Michal Marek <mmarek@suse.cz>
Subject: Re: [PATCH V2 0/7] kbuild: move scripts/basic/docproc.c to scripts/docproc.c
Date: Fri, 29 Apr 2011 20:30:23 -0400 [thread overview]
Message-ID: <4DBB581F.2080607@verizon.net> (raw)
In-Reply-To: <20110429161853.772ee28d.rdunlap@xenotime.net>
On 4/29/2011 7:18 PM, Randy Dunlap wrote:
> On Fri, 29 Apr 2011 19:09:02 -0400 Peter Foley wrote:
>
>
>> See https://lkml.org/lkml/2011/4/29/89 for the attachment request.
>> My current email client (thunderbird) seems to mangle any patches that I send.
>> If anybody can suggest an email client that doesn't mangle patches I'll be happy to try it.
>
> Have you tried any hints in Documentation/email-clients.txt for thunderbird?
>
> I can send patches successfully with thunderbird 3.0 (on Linux).
>
> or it could just be verizon helping out too much. :(
>
> ---
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
I tried the hints but still seem to be having issues.
So, I think I'll try using git send-email as suggested by Arnaud Lacombe.
Thanks for the help.
Peter
next prev parent reply other threads:[~2011-04-30 0:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 22:38 [PATCH V2 0/7] kbuild: move scripts/basic/docproc.c to scripts/docproc.c Peter Foley
2011-04-29 22:46 ` Randy Dunlap
2011-04-29 23:00 ` Michal Marek
2011-04-29 23:02 ` Randy Dunlap
2011-04-29 23:15 ` Peter Foley
2011-04-29 23:09 ` Peter Foley
2011-04-29 23:18 ` Randy Dunlap
2011-04-30 0:30 ` Peter Foley [this message]
2011-04-29 23:22 ` Arnaud Lacombe
2011-04-29 22:59 ` Randy Dunlap
2011-04-29 23:00 ` Randy Dunlap
2011-04-29 23:04 ` Randy Dunlap
2011-05-02 20:55 ` Michal Marek
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=4DBB581F.2080607@verizon.net \
--to=pefoley2@verizon.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rdunlap@xenotime.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