Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs git repos available
Date: Thu, 25 Sep 2008 17:06:28 -0400	[thread overview]
Message-ID: <1222376788.7028.83.camel@think.oraclecorp.com> (raw)
In-Reply-To: <1222282963.7160.210.camel@think.oraclecorp.com>

On Wed, 2008-09-24 at 15:02 -0400, Chris Mason wrote:
> Hello everyone,
> 
> As part of moving toward mainline, I've changed the Btrfs repositories
> over to git.  So far I've only converted the unstable repositories
> (thanks to some help from David Woodhouse, who already had -git forms of
> things).
> 
> The progs-unstable repo is a direct clone of David's git repo.  The
> kernel one has btrfs grafted into fs/btrfs.  All compatibility code for
> older kernels has been removed.
> 
> I'll construct repos in git of btrfs as a stand alone module, and that
> will include the compatibility code.
> 
> These git repos are not yet final, I may rebase them or redo them.  But,
> all new patches are going into them instead of the mercurial repos.
> 

Well, after some hints from Linus I've rebased these about 4 times now.
The new changesets are generally cleaner and are setup properly under
fs/btrfs.

So, if you were using a tree pulled before Thursday afternoon, please
delete it and clone again.  The btrfs-progs repo is unchanged.

> Kernel:
> 
> http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-unstable.git;a=summary
> 
> Progs:
> 
> http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-progs-unstable.git;a=summary
> 

-chris



  reply	other threads:[~2008-09-25 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24 19:02 Btrfs git repos available Chris Mason
2008-09-25 21:06 ` Chris Mason [this message]
2008-09-25 21:25   ` Zach Brown
2008-09-26  1:08     ` Chris Mason

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=1222376788.7028.83.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --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