From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: New branches for linux-next
Date: Thu, 22 Jul 2010 21:10:19 -0700 [thread overview]
Message-ID: <4C49162B.9070407@goop.org> (raw)
In-Reply-To: <20100723111018.f250c0f5.sfr@canb.auug.org.au>
On 07/22/2010 06:10 PM, Stephen Rothwell wrote:
> Added starting today. I put just you as the contact - I can add more
> people/lists if you like.
>
Thanks. Please add "Xen Devel <Xen-devel@lists.xensource.com>" to the
contact list.
J
next prev parent reply other threads:[~2010-07-23 4:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 23:52 New branches for linux-next Jeremy Fitzhardinge
2010-07-23 1:10 ` Stephen Rothwell
2010-07-23 4:10 ` Jeremy Fitzhardinge [this message]
2010-07-23 7:00 ` Stephen Rothwell
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=4C49162B.9070407@goop.org \
--to=jeremy@goop.org \
--cc=Xen-devel@lists.xensource.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=stefano.stabellini@eu.citrix.com \
/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