[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4DBB450E.7080208@verizon.net>
Date: Fri, 29 Apr 2011 19:09:02 -0400
From: Peter Foley <pefoley2@...izon.net>
To: Randy Dunlap <rdunlap@...otime.net>
CC: <linux-kernel@...r.kernel.org>, <linux-kbuild@...r.kernel.org>,
Michal Marek <mmarek@...e.cz>
Subject: Re: [PATCH V2 0/7] kbuild: move scripts/basic/docproc.c to scripts/docproc.c
On 4/29/2011 6:46 PM, Randy Dunlap wrote:
> On Fri, 29 Apr 2011 18:38:12 -0400 Peter Foley wrote:
>
>> This patchset moves scripts/basic/docproc to scripts/docproc.
>> This causes docproc to only be built for *doc targets rather than every
>> time the kernel is compiled.
>>
>> Patches also attached as requested by Michal Marek.
>
>
> That's disappointing (the attachments). Why was this requested?
>
> See Documentation/CodingStyle, section 7:
>
> "No MIME, no links, no compression, no attachments. Just plain text."
>
>
> It also causes breakage in other people's patch merging/testing.
> E.g., I cannot save any one of these emails as I can with other patches
> and get a useful patch file. Instead, the saved file contains lines like
> this (below) and each patch 2 times (inline and attachment).
>
> --------------060706070408040606010200
> Content-Type: text/plain;
> name="kbuild-update-DocBook-Makefile-in-preperation-for-mo.patch"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: attachment;
> filename="kbuild-update-DocBook-Makefile-in-preperation-for-mo.patch"
>
>
>
> ---
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
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.
Thanks,
Peter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists