From: Andi Kleen <ak@suse.de>
To: Chris Wright <chrisw@sous-sol.org>
Cc: virtualization@lists.osdl.org
Subject: Re: What do we need to do to hit 2.6.19?
Date: Sat, 5 Aug 2006 00:38:57 +0200 [thread overview]
Message-ID: <200608050038.57370.ak@suse.de> (raw)
In-Reply-To: <20060804222147.GP2654@sequoia.sous-sol.org>
> I don't agree. We've got the first bit of obvious stuff posted
For some value of "posted" that includes destroying it with rogue MIME
encoding.
> and
> queued up.
Yes and you missed the testing phase so far completely.
Merge window is not really the time to push in lots of fresh untested
code.
-Andi
next prev parent reply other threads:[~2006-08-04 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44D39351.9070405@goop.org>
2006-08-04 22:14 ` What do we need to do to hit 2.6.19? Andi Kleen
2006-08-04 22:21 ` Chris Wright
2006-08-04 22:38 ` Andi Kleen [this message]
2006-08-04 23:50 ` Chris Wright
2006-08-05 1:45 ` Jeremy Fitzhardinge
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=200608050038.57370.ak@suse.de \
--to=ak@suse.de \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.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;
as well as URLs for NNTP newsgroup(s).