From: Chris Mason <chris.mason@oracle.com>
To: Chris Samuel <chris@csamuel.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Definitive btrfs git tree ?
Date: Mon, 12 Jan 2009 16:28:21 -0500 [thread overview]
Message-ID: <1231795701.22806.42.camel@think.oraclecorp.com> (raw)
In-Reply-To: <200901130726.08242.chris@csamuel.org>
On Tue, 2009-01-13 at 07:26 +1100, Chris Samuel wrote:
> Hi Chris,
>
> Now btrfs has made it into the mainline, which git tree is definitive now ?
Only mainline is definitive ;)
We'll have a tree with stable fixes that we want Linus to pull, and
we'll have a development tree with unstable experimental stuff (these
aren't yet named).
For the progs, the btrfs-progs-unstable tree is up to date and safe.
I'll make something with a less scary name later this week, and save the
unstable tree for development.
-chris
next prev parent reply other threads:[~2009-01-12 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 20:26 Definitive btrfs git tree ? Chris Samuel
2009-01-12 21:28 ` Chris Mason [this message]
2009-01-13 7:24 ` Chris Samuel
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=1231795701.22806.42.camel@think.oraclecorp.com \
--to=chris.mason@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