linux-kernel - Re: [PATCH V2 0/7] kbuild: move scripts/basic/docproc.c to scripts/docproc.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 29 Apr 2011 15:46:49 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	<pefoley2@...izon.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 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 ***
--
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/