public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Rik van Riel <riel@redhat.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Chris Friesen <cfriesen@nortel.com>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	lkml <linux-kernel@vger.kernel.org>,
	akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH/RFC] doc: about email clients for Linux kernel patches
Date: Wed, 12 Sep 2007 21:53:00 +0200	[thread overview]
Message-ID: <1189626781.5597.2.camel@lappy> (raw)
In-Reply-To: <46E83B16.2070608@redhat.com>


On Wed, 2007-09-12 at 15:16 -0400, Rik van Riel wrote:
> Jeff Garzik wrote:
> > Chris Friesen wrote:
> >> Randy Dunlap wrote:
> >>
> >>> +Thunderbird (GUI)
> >>> +
> >>> +By default, thunderbird likes to mangle text, but there are ways to
> >>> +coerce it into being nice.
> >>
> >> Can someone describe the problems with just attaching the patch in 
> >> Thunderbird?  It's what Martin says he does on the linked document...
> > 
> > Email clients don't like to quote attachments, even text/plain ones, 
> > which then makes attached patches much more difficult to review and 
> > comment on (i.e. you greatly reduce the number of reviewers).
> 
> Interestingly, Thunderbird does this right and simply
> adds text/plain attachments to the quoted text.
> 

Devolution allows the same, but most other mailers dont. Esp the text
based onces which are the majority under the people you want reviews
from.


  reply	other threads:[~2007-09-12 19:53 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11 17:16 [PATCH/RFC] doc: about email clients for Linux kernel patches Randy Dunlap
2007-09-11 17:36 ` Peter Zijlstra
2007-09-11 18:38   ` Lee Revell
2007-09-11 18:52     ` Peter Zijlstra
2007-09-12  5:07       ` WANG Cong
2007-09-11 22:05     ` Sami Farin
2007-09-12  3:40   ` Randy Dunlap
2007-09-11 18:03 ` Nicolas Pitre
2007-09-11 18:17   ` Adrian Bunk
2007-09-11 18:31     ` Nicolas Pitre
2007-09-11 18:46       ` Adrian Bunk
2007-09-11 19:09     ` Jan Engelhardt
2007-09-11 19:08   ` Jan Engelhardt
2007-09-11 18:29 ` Adrian Bunk
2007-09-12  5:24   ` WANG Cong
2007-09-12  5:55     ` Adrian Bunk
2007-09-12 15:02       ` Randy Dunlap
2007-09-12 15:43         ` Adrian Bunk
2007-09-11 19:37 ` Chris Friesen
2007-09-11 19:42   ` Martin Bligh
2007-09-11 19:55   ` Jeff Garzik
2007-09-12  3:26     ` Chris Friesen
2007-09-12 18:08       ` Jan Engelhardt
2007-09-12 18:17         ` Chris Friesen
2007-09-12 22:35           ` Stefan Richter
2007-09-12 19:16     ` Rik van Riel
2007-09-12 19:53       ` Peter Zijlstra [this message]
2007-09-12 23:09         ` Adrian Bunk
2007-09-11 19:54 ` Stefan Richter

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=1189626781.5597.2.camel@lappy \
    --to=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=cfriesen@nortel.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=riel@redhat.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