All of lore.kernel.org
 help / color / mirror / Atom feed
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 19:09:02 -0400	[thread overview]
Message-ID: <4DBB450E.7080208@verizon.net> (raw)
In-Reply-To: <20110429154649.848f9ba8.rdunlap@xenotime.net>

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

WARNING: multiple messages have this Message-ID (diff)
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 19:09:02 -0400	[thread overview]
Message-ID: <4DBB450E.7080208@verizon.net> (raw)
In-Reply-To: <20110429154649.848f9ba8.rdunlap@xenotime.net>

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

  parent reply	other threads:[~2011-04-29 23:09 UTC|newest]

Thread overview: 22+ 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:38 ` Peter Foley
2011-04-29 22:46 ` Randy Dunlap
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:15         ` Peter Foley
2011-04-29 23:09   ` Peter Foley [this message]
2011-04-29 23:09     ` Peter Foley
2011-04-29 23:18     ` Randy Dunlap
2011-04-29 23:18       ` Randy Dunlap
2011-04-30  0:30       ` Peter Foley
2011-04-30  0:30         ` Peter Foley
2011-04-29 23:22     ` Arnaud Lacombe
2011-04-29 22:59 ` Randy Dunlap
2011-04-29 22:59   ` Randy Dunlap
2011-04-29 23:00   ` Randy Dunlap
2011-04-29 23:00     ` Randy Dunlap
2011-04-29 23:04     ` 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=4DBB450E.7080208@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.