From: Alexander Nyberg <alexn@dsv.su.se>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Chris Wright <chrisw@osdl.org>,
Valdis.Kletnieks@vt.edu,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] update SubmittingPatches to clarify attachment policy
Date: Wed, 04 May 2005 21:21:53 +0200 [thread overview]
Message-ID: <1115234513.2562.32.camel@localhost.localdomain> (raw)
In-Reply-To: <1115230450.22718.14.camel@localhost>
ons 2005-05-04 klockan 11:14 -0700 skrev Dave Hansen:
> On Wed, 2005-05-04 at 10:55 -0700, Chris Wright wrote:
> > I agree that things are better. But, ironically, this patch is a case
> > in point. It's attached as text/x-patch and makes replying to and
> > commenting on patch inline more laborious.
>
> Well, crap.
>
> I've sent an awful lot of patches that way, and never had a negative
> reply from a maintainer or a patch commenter.
>
> As an aside: is there a proper way to do patch text/plain attachments
> from Evolution? Maybe we need a quick tutorial on what the best way to
> send patches is with several popular mailers.
>
In evolution I just do new mail => insert => text file and change the
mail to preformat instead of normal formatting. I'm sure there are
settings somewhere to make this default but I don't send enough patches
(yet) to bother, the output works anyway (old patch shown below):
Index: linux-2.6/arch/x86_64/kernel/head64.c
===================================================================
--- linux-2.6.orig/arch/x86_64/kernel/head64.c 2005-04-26 11:41:43.000000000 +0200
+++ linux-2.6/arch/x86_64/kernel/head64.c 2005-04-29 11:57:46.000000000 +0200
@@ -93,9 +93,6 @@
#ifdef CONFIG_SMP
cpu_set(0, cpu_online_map);
#endif
- /* default console: */
- if (!strstr(saved_command_line, "console="))
- strcat(saved_command_line, " console=tty0");
s = strstr(saved_command_line, "earlyprintk=");
if (s != NULL)
setup_early_printk(s);
next prev parent reply other threads:[~2005-05-04 19:22 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 [this message]
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
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=1115234513.2562.32.camel@localhost.localdomain \
--to=alexn@dsv.su.se \
--cc=Valdis.Kletnieks@vt.edu \
--cc=chrisw@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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