From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: Definitive btrfs git tree ?
Date: Tue, 13 Jan 2009 18:24:54 +1100 [thread overview]
Message-ID: <200901131825.01026.chris@csamuel.org> (raw)
In-Reply-To: <1231795701.22806.42.camel@think.oraclecorp.com>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
On Tue, 13 Jan 2009 8:28:21 am Chris Mason wrote:
> Only mainline is definitive ;)
Oh ha ha! ;-)
> 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).
Ah, so for the moment stick with btrfs-unstable-standalone ?
> 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.
Cool, not scary is good (though I'm happy to stay with the scary one).
cheers,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 481 bytes --]
prev parent reply other threads:[~2009-01-13 7:24 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
2009-01-13 7:24 ` Chris Samuel [this message]
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=200901131825.01026.chris@csamuel.org \
--to=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