From: Hans Schou <linux@schou.dk>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SiS55x, another x86 CPU
Date: Thu, 16 Oct 2008 22:13:06 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0810162201150.7314@sko.w0.dk> (raw)
In-Reply-To: <alpine.LFD.1.10.0810162014590.21444@ftp.linux-mips.org>
On Thu, 16 Oct 2008, Maciej W. Rozycki wrote:
> On Thu, 16 Oct 2008, Hans Schou wrote:
>
> > > But, why do you send patches as attachments in the first place?
> >
> > Ingo said I could do so when it was something to do with x86 patches.
> > Anyway, it looks like ^R in Pine did work correctly.
>
> You've got:
>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Thanks:
[X] quell-flowed-text
> in your headers -- it may be good for poetry, but will guarantee you
> breakage with inline patches. There's an option to disable it.
Maybe I should start on poetry instead of kernel-patching.
"Tired of bugs?
Then try Linux."
...I don't think I can do that for a living.
/hans
next prev parent reply other threads:[~2008-10-16 20:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 21:24 Hans Schou
2008-10-13 5:58 ` Andi Kleen
2008-10-13 20:56 ` Hans Schou
2008-10-14 6:06 ` Andi Kleen
2008-10-14 17:38 ` Hans Schou
2008-10-15 10:06 ` Andi Kleen
2008-10-15 19:51 ` Geert Uytterhoeven
2008-10-15 22:37 ` Hans Schou
2008-10-16 7:09 ` Geert Uytterhoeven
2008-10-16 19:01 ` Hans Schou
2008-10-16 19:18 ` Maciej W. Rozycki
2008-10-16 20:13 ` Hans Schou [this message]
2008-10-15 22:24 ` Hans Schou
[not found] ` <48F6E3DE.10206@zytor.com>
2008-10-16 18:47 ` Hans Schou
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=Pine.LNX.4.64.0810162201150.7314@sko.w0.dk \
--to=linux@schou.dk \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.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
all inboxes | Powered by JetHome®