Re: no activity in kernel.org btrfs-progs git repo?

[Hugo Mills <hugo@carfax.org.uk>]

[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]

On Thu, Dec 13, 2012 at 04:50:54AM +0530, Nirbheek Chauhan wrote:
> On Thu, Dec 13, 2012 at 4:21 AM, Hugo Mills <hugo@carfax.org.uk> wrote:
> >    Two things:
> >
> > 1) That tree is generally only ever updated for pull requests to Linus
> >    during the merge window. Would that it were otherwise, but I
> >    suspect that...
> >
> > 2) ... you may want to know about josef's btrfs-next tree:
> >
> > https://btrfs.wiki.kernel.org/index.php/Btrfs_source_repositories#Integration_repository_.28btrfs-next.29
> >
> >    It's regarded as fairly unstable, so only run it on systems for
> > testing purposes (or if josef tells you it's OK and will fix one of
> > your problems).
> >
> 
> I think Zach was asking about the userspace tools, not the kernel
> module. That link points to the kernel module integration branches,
> and the link above that on the wiki page about btrfs-progs integration
> hasn't had commits in the last 6 months, AFAICT.
> 
> I've been concerned about the status btrfs-progs maintenance myself.
> I've seen quite a few obvious bugs about btrfs-progs on this list in
> the past months—most of them with patches. However, I don't see them
> enter any upstream git repositories.

   D'oh. It's been a long day... Must learn to read more carefully.
Sorry.

   I've been a combination of ill and busy (mostly busy) for the last
umpteen months, which is why the integration repo hasn't been updated.
The main -progs repo doesn't get a whole lot of love, even when I've
managed to do an integration run and hold it together for long enough
for Chris to pick it up. Patches do eventually get in, but it's
usually on a 6+-month cycle.

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
     --- IMPROVE YOUR ORGANISMS!!  -- Subject line of spam email ---     

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]