From: "Chris Schlaeger" <Chris.Schlaeger@amd.com>
To: discuss@x86-64.org
Cc: "Andi Kleen" <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [discuss] x86_64: x86-64 mailing lists / posting patchkits / x86-64 releases
Date: Mon, 12 Jun 2006 16:05:07 +0200 [thread overview]
Message-ID: <200606121605.08869.Chris.Schlaeger@amd.com> (raw)
In-Reply-To: <200606121307.54556.ak@suse.de>
It's probably a good idea to move the bulk of the patches to the patches list.
This will probably increase the attractiveness of the discuss list.
Regarding the testing, I'm trying to find one or two people who can help you
with this. We have an interest to keep the -mm submissions in good shape.
Just give me a few more weeks.
Chris
next prev parent reply other threads:[~2006-06-12 14:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 11:07 x86_64: x86-64 mailing lists / posting patchkits / x86-64 releases Andi Kleen
2006-06-12 11:18 ` [discuss] " Jan Beulich
2006-06-12 14:05 ` Chris Schlaeger [this message]
2006-06-12 23:33 ` Ravikiran G Thirumalai
2006-06-13 0:35 ` Nigel Cunningham
2006-06-13 8:02 ` Muli Ben-Yehuda
2006-06-17 17:05 ` Andrew Morton
2006-06-18 7:35 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-06-12 14:11 [discuss] " Langsdorf, Mark
2006-06-12 15:44 ` Randy.Dunlap
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=200606121605.08869.Chris.Schlaeger@amd.com \
--to=chris.schlaeger@amd.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--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