linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-btrfs@vger.kernel.org, btrfs-devel@oss.oracle.com
Subject: Btrfs hosting moving to kernel.org
Date: Tue, 1 Apr 2008 14:16:43 -0400	[thread overview]
Message-ID: <200804011416.43563.chris.mason@oracle.com> (raw)

Hello everyone,

I have setup new locations for the Btrfs sources, mailing lists and web pages 
on kernel.org.  The old pages on oss.oracle.com are still live but I'll 
change things soon to point to the new location.

Btrfs resources from Oracle haven't changed, and we still have an aggressive 
development plan to get things production ready.  The move to kernel.org will 
hopefully increase the project's profile a bit, and make it easier for us to 
collaborate with others interested in filesystem development.

(thanks to the kernel.org admins for all of their help!)

Main Btrfs project page:

http://btrfs.wiki.kernel.org/

Sources:

http://www.kernel.org/hg/btrfs/
http://www.kernel.org/pub/linux/kernel/people/mason/btrfs/

Mailing list

linux-btrfs@vger.kernel.org

People on the current btrfs mailing lists will have to subscribe to the new 
list on vger.  You can find more details on subscribing to the vger lists 
here:

http://vger.kernel.org/majordomo-info.html

And the Btrfs list here:

http://vger.kernel.org/vger-lists.html#linux-btrfs

The short version is to send a message to majordomo@vger.kernel.org with:

subscribe linux-btrfs

In the body.

-chris


             reply	other threads:[~2008-04-01 18:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 18:16 Chris Mason [this message]
2008-07-20 23:59 ` Btrfs hosting moving to kernel.org 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=200804011416.43563.chris.mason@oracle.com \
    --to=chris.mason@oracle.com \
    --cc=btrfs-devel@oss.oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).