From: Lee Revell <rlrevell@joe-job.com>
To: Steven Cole <elenstev@mesatop.com>
Cc: Paulo Marques <pmarques@grupopie.com>,
Krzysztof Halasa <khc@pm.waw.pl>, Rik van Riel <riel@redhat.com>,
Dave Hansen <haveblue@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] update SubmittingPatches to clarify attachment policy
Date: Thu, 05 May 2005 21:31:30 -0400 [thread overview]
Message-ID: <1115343090.28496.9.camel@mindpipe> (raw)
In-Reply-To: <427A9169.6050300@mesatop.com>
On Thu, 2005-05-05 at 15:34 -0600, Steven Cole wrote:
> Paulo Marques wrote:
> >
> > However if we Copy+Paste the patch into the mail it gets line wrapped /
> > white space mangled.
>
> That depends on where you are Copy+Pasting from. Granted, Copy+Paste from
> a variety of sources is a nightmare. But, Copy+Paste from Tbird to Tbird
> seems to actually work.
>
> >
> > So at least for Thunderbird users it would be better to use attached
> > patches with "Content-Disposition: inline".
> >
>
> Here is a trick you can play with Thunderbird to get inlined patches:
>
> 1) Mail the patch to yourself as an attachment.
> 2) Read the mail you just got, copy and paste the patch to your new message.
>
> This method preserves the tabs/whitespace. Of course, you have to set the
> wordwrap settings appropriately. It works for me.
Personally, I don't understand people who can hack the kernel but
complain about bugs in their mail client.
Lee
next prev parent reply other threads:[~2005-05-06 1:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 17:01 [RFC][PATCH] update SubmittingPatches to clarify attachment policy Dave Hansen
2005-05-04 17:10 ` Jon Smirl
2005-05-04 17:54 ` Jan-Benedict Glaw
2005-05-04 18:23 ` Richard B. Johnson
2005-05-05 8:12 ` Jan-Benedict Glaw
2005-05-05 16:43 ` Lee Revell
2005-05-05 17:31 ` Jan-Benedict Glaw
2005-05-04 20:42 ` Rafael J. Wysocki
2005-05-04 17:15 ` Dmitry Torokhov
2005-05-04 17:16 ` Valdis.Kletnieks
2005-05-04 17:25 ` Dave Hansen
2005-05-04 17:55 ` Chris Wright
2005-05-04 18:14 ` Dave Hansen
2005-05-04 19:21 ` Alexander Nyberg
2005-05-05 19:06 ` Jeff Garzik
2005-05-04 17:58 ` Dipankar Sarma
2005-05-04 18:52 ` Krzysztof Halasa
2005-05-04 19:28 ` Randy.Dunlap
2005-05-14 22:10 ` Domen Puncer
2005-05-04 17:59 ` John W. Linville
2005-05-05 1:09 ` Rik van Riel
2005-05-05 9:07 ` Geert Uytterhoeven
2005-05-05 10:06 ` Krzysztof Halasa
2005-05-05 12:01 ` Paulo Marques
2005-05-05 21:34 ` Steven Cole
2005-05-06 1:31 ` Lee Revell [this message]
2005-05-06 4:05 ` Valdis.Kletnieks
[not found] <40vxU-1a1-25@gated-at.bofh.it>
[not found] ` <40vRd-1os-1@gated-at.bofh.it>
2005-05-05 2:36 ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
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=1115343090.28496.9.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=elenstev@mesatop.com \
--cc=haveblue@us.ibm.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=pmarques@grupopie.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 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.