From: Willy Tarreau <willy@w.ods.org>
To: Mike Galbraith <efault@gmx.de>
Cc: lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@osdl.org>,
Peter Williams <pwil3058@bigpond.net.au>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Con Kolivas <kernel@kolivas.org>
Subject: Re: [rfc][patch] improved interactive starvation patch against 2.6.16
Date: Thu, 30 Mar 2006 16:53:24 +0200 [thread overview]
Message-ID: <20060330145324.GB4914@w.ods.org> (raw)
In-Reply-To: <1143728558.7840.11.camel@homer>
On Thu, Mar 30, 2006 at 04:22:38PM +0200, Mike Galbraith wrote:
> You applied the wrong patch. The inlined one was against virgin 2.6.16,
> for folks to comment on, and the attached was the incremental against
> the 2.6.16 anti-starvation tree.
>
> Ah, your mailer probably showed both as attached. Anyway, here's the
> incremental again inlined.
Ah OK, it's not even the mailer, it's me. I read the message and did not
notice the attachment, just the inline patch. Then I forwarded it to my
work address and lost the attachment. You know the rest ...
> (note to self: never include patches for two trees in same message)
Good advice. Or manually edit the directory name in the diff to
explicitly show what it refers to. Eg:
--- linux-2.6.16-sched7/kernel/sched.c 2006-03-27 06:11:01.000000000 +0200
+++ linux-2.6.16/kernel/sched.c 2006-03-30 10:50:46.000000000 +0200
Anyway, thanks for your reply, I'll re-apply it and recompile.
> -Mike
Cheers,
Willy
next prev parent reply other threads:[~2006-03-30 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 10:19 [rfc][patch] improved interactive starvation patch against 2.6.16 Mike Galbraith
2006-03-30 11:07 ` Willy Tarreau
2006-03-30 11:55 ` Willy Tarreau
2006-03-30 14:22 ` Mike Galbraith
2006-03-30 14:53 ` Willy Tarreau [this message]
2006-03-30 18:23 ` Mike Galbraith
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=20060330145324.GB4914@w.ods.org \
--to=willy@w.ods.org \
--cc=akpm@osdl.org \
--cc=efault@gmx.de \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pwil3058@bigpond.net.au \
/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