From: Chris Mason <chris.mason@fusionio.com>
To: Zach Brown <zab@zabbo.net>
Cc: Chris Mason <clmason@fusionio.com>,
Nirbheek Chauhan <nirbheek.chauhan@gmail.com>,
Hugo Mills <hugo@carfax.org.uk>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: no activity in kernel.org btrfs-progs git repo?
Date: Thu, 13 Dec 2012 16:06:28 -0500 [thread overview]
Message-ID: <20121213210628.GB27308@shiny> (raw)
In-Reply-To: <20121213195040.GE9195@lenny.home.zabbo.net>
On Thu, Dec 13, 2012 at 12:50:40PM -0700, Zach Brown wrote:
> On Thu, Dec 13, 2012 at 09:56:10AM -0500, Chris Mason wrote:
> >
> > Yes, I've got the big raid56 push ready to go out, and I've just been
> > trying to test it all. I'll put that in a raid branch and get the fixes
> > onto master.
>
> Thanks.
>
> I was asking because it's pretty annoying to go through patchwork to see
> if someone else has already fixed bugs in the git tree. This happened
> to me when our distro package infrastructure freaked out at btrfs-progs
> (-fno-strict-aliasing, int/ptr differences, static code analysis
> lighting up a like a christmas tree).
>
> Would it be fair to say that the project is accepting applications for
> an active btrfs-progs maintainer? :)
Well, the problem is the active maintainer is busy piling in other
features. But yeah, I need to pull in the fixes, sorry.
-chris
next prev parent reply other threads:[~2012-12-13 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 22:42 no activity in kernel.org btrfs-progs git repo? Zach Brown
2012-12-12 22:51 ` Hugo Mills
2012-12-12 23:20 ` Nirbheek Chauhan
2012-12-12 23:41 ` Zach Brown
2012-12-13 14:56 ` Chris Mason
2012-12-13 19:50 ` Zach Brown
2012-12-13 21:06 ` Chris Mason [this message]
2012-12-12 23:51 ` Hugo Mills
2012-12-14 18:04 ` Piotr Pawłow
2012-12-14 18:31 ` Hendrik Friedel
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=20121213210628.GB27308@shiny \
--to=chris.mason@fusionio.com \
--cc=clmason@fusionio.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=nirbheek.chauhan@gmail.com \
--cc=zab@zabbo.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.