public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Bill Davidsen <davidsen@tmr.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Jonathan Campbell <jon@nerdgrounds.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Patches for tiny 386 kernels, again. Linux kernel   2.6.22.7
Date: Mon, 1 Oct 2007 09:44:05 -0400	[thread overview]
Message-ID: <20071001134405.GA16330@csclub.uwaterloo.ca> (raw)
In-Reply-To: <46FD7104.9070609@tmr.com>

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

  parent reply	other threads:[~2007-10-01 13:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-24  8:51 [PATCH] Patches for tiny 386 kernels, again. Linux kernel 2.6.22.7 Jonathan Campbell
2007-09-24 17:49 ` Randy Dunlap
2007-09-26 18:42   ` Jonathan Campbell
2007-09-26 22:06     ` Randy Dunlap
2007-09-26 23:20     ` Randy Dunlap
2007-09-26 23:44       ` Jonathan Campbell
     [not found]       ` <46FAEE97.7090902@nerdgrounds.com>
2007-09-26 23:47         ` Randy Dunlap
2007-09-26 23:49           ` Jonathan Campbell
2007-09-28 21:24   ` Bill Davidsen
2007-09-28 21:56     ` Randy Dunlap
2007-10-01 13:44     ` Lennart Sorensen [this message]
2007-10-01 14:28       ` Bill Davidsen
2007-10-02  4:48         ` Willy Tarreau
2007-09-24 19:09 ` Dave Jones
2007-09-25  4:45   ` Andrey Panin
2007-09-25  7:28   ` Jan Engelhardt

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=20071001134405.GA16330@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=davidsen@tmr.com \
    --cc=jon@nerdgrounds.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    /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