From: Hugo Mills <hugo@carfax.org.uk>
To: Zach Brown <zab@zabbo.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: no activity in kernel.org btrfs-progs git repo?
Date: Wed, 12 Dec 2012 22:51:57 +0000 [thread overview]
Message-ID: <20121212225157.GD19051@carfax.org.uk> (raw)
In-Reply-To: <20121212224214.GA9195@lenny.home.zabbo.net>
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
On Wed, Dec 12, 2012 at 02:42:14PM -0800, Zach Brown wrote:
> It looks like it's been a bit more than two months since
>
> http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-progs.git;a=summary
>
> saw patches from the list.
>
> Am I looking in the wrong place for the btrfs-progs upstream?
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).
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
--- Do not meddle in the affairs of wizards, for they are subtle, ---
and quick to anger.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-12-12 22:52 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 [this message]
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
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=20121212225157.GD19051@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--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.