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]
Message-ID: <20071001134405.GA16330@csclub.uwaterloo.ca>
Date:	Mon, 1 Oct 2007 09:44:05 -0400
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	Bill Davidsen <davidsen@....com>
Cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	Jonathan Campbell <jon@...dgrounds.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Patches for tiny 386 kernels, again. Linux kernel   2.6.22.7

On Fri, Sep 28, 2007 at 05:24:20PM -0400, Bill Davidsen wrote:
> I'll offer this suggestion, knowing it may piss you off, given the 
> difficulty of preserving whitespace on *many* mailers without using 
> attachments, and given that attachments can be saved easily without 
> prying them out of the message, why don't you (one person) switch to a 
> capable mail agent, if only for patches, instead of trying to teach many 
> people to jump through hoops to avoid whitespace issues?
> 
> Not criticizing, just seems easier for everybody for you to avoid 
> teaching people things they don't find useful elsewhere, or getting 
> discouraged and not bothering.

Ehm, so you want people to save the patch, then when replying they
should load the patch into their (much better) mail client where they
can comment on the patch?  That is the reason the patch should be
inline.  People need to comment on it just as they would comment on any
other plain text email.

Well that and some people use git to import patches from the email in a
mostly automated way which also expects them to have the info at top
with signed-off and then the patch, which attachments also screw up.

So yes there are good reasons for getting a non broken mail client when
sending patches to lkml.

--
Len Sorensen
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ