From: Chris Mason <chris.mason@oracle.com>
To: btrfs-devel@oss.oracle.com
Cc: Chris Samuel <chris@csamuel.org>, linux-btrfs@vger.kernel.org
Subject: Re: [Btrfs-devel] Btrfs hosting moving to kernel.org
Date: Fri, 25 Apr 2008 08:45:33 -0400 [thread overview]
Message-ID: <200804250845.33472.chris.mason@oracle.com> (raw)
In-Reply-To: <200804252226.34660.chris@csamuel.org>
On Friday 25 April 2008, Chris Samuel wrote:
> Hi Chris,
>
> What are your plans for the old lists ?
>
> I've subscribed to both and seem to only get duplicate traffic from
> the old list on the Vger list, and some people only post to the
> Oracle one.
I'm working with the Oracle admins to turn the Oracle ones off, and post some
kind of nice redirect on the web pages.
-chris
next prev parent reply other threads:[~2008-04-25 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 18:16 Btrfs hosting moving to kernel.org Chris Mason
2008-04-25 12:26 ` [Btrfs-devel] " Chris Samuel
[not found] ` <200804252226.34660.chris@csamuel.org>
2008-04-25 12:45 ` Chris Mason [this message]
2008-07-20 23:59 ` David Woodhouse
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=200804250845.33472.chris.mason@oracle.com \
--to=chris.mason@oracle.com \
--cc=btrfs-devel@oss.oracle.com \
--cc=chris@csamuel.org \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).