From: Hugo Mills <hugo@carfax.org.uk>
To: Suman C <schakrava@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs-Progs integration branch question
Date: Mon, 3 Sep 2012 17:57:23 +0100 [thread overview]
Message-ID: <20120903165723.GI21990@carfax.org.uk> (raw)
In-Reply-To: <CAPF83mvX6ueqaR62bvRygapGtw6RPuSTo1+oeYUrYAD0MPsULA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
On Mon, Sep 03, 2012 at 09:31:16AM -0700, Suman C wrote:
> Hi,
>
> I would like to get the latest btrfs-progs code. To me, Chris Mason's
> repo at git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git
> seems latest but obviously its missing the last several patches I see
> in the mailing list. I also tried Hugo Mills' integration repo at
> http://git.darksatanic.net/repo/btrfs-progs-unstable.git and unless I
> am looking at it wrong, it seems behind.
It is. I'm out of date.
> Can someone please point me to the latest process that is followed for
> testing/developing recent btrfs-progs?
Chris's repo, right now.
> I am trying to integrate the quota patch from August 10th by Jan
> Schmidt and getting conflicts when I git apply.
Good luck. :)
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
--- What do you give the man who has everything? -- Penicillin is ---
a good start...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2012-09-03 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 16:31 Btrfs-Progs integration branch question Suman C
2012-09-03 16:57 ` Hugo Mills [this message]
2012-09-04 9:23 ` Jan Schmidt
2012-09-04 16:12 ` 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=20120903165723.GI21990@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=schakrava@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).