From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs-progs: allow --init-extent-tree to work when extent tree is borked
Date: Tue, 19 Nov 2013 06:25:52 +0000 [thread overview]
Message-ID: <l6f095$euo$1@ger.gmane.org> (raw)
In-Reply-To: <l5eq5s$m8l$1@ger.gmane.org>
On 07/11/13 01:25, Martin wrote:
[...]
> And the patching fails due to mismatching code...
>
> I have the Gentoo source for:
>
> Btrfs v0.20-rc1-358-g194aa4a
>
> (On Gentoo 3.11.5, will be on 3.11.6 later today.)
>
>
> What are the magic incantations to download your version of source code
> to try please? (Patched or unpatched?)
As an FYI for anyone stumbling onto this thread:
See:
https://btrfs.wiki.kernel.org/index.php/Btrfs_source_repositories
to get to the code!
Cheers,
Martin
prev parent reply other threads:[~2013-11-19 6:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 18:01 [PATCH] Btrfs-progs: allow --init-extent-tree to work when extent tree is borked Josef Bacik
2013-10-25 18:27 ` Martin
2013-10-25 18:31 ` Josef Bacik
2013-10-26 23:16 ` Martin
2013-10-27 1:44 ` Josef Back
2013-10-28 15:11 ` Josef Bacik
2013-11-07 1:25 ` Martin
2013-11-11 22:52 ` Martin
2013-11-13 12:08 ` Martin
2013-11-13 13:46 ` Duncan
2013-11-15 17:18 ` Martin
2013-11-19 6:34 ` Martin
2013-11-20 6:51 ` btrfsck --repair /dev/sdc (Was: [PATCH] Btrfs-progs: allow --init-extent-tree to work when extent tree is borked) Martin
2013-11-20 17:08 ` Duncan
2013-11-20 20:00 ` Martin
2013-11-25 23:18 ` Martin
2013-11-27 6:29 ` Martin
2013-11-20 20:03 ` Martin
2013-11-19 6:25 ` Martin [this message]
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='l6f095$euo$1@ger.gmane.org' \
--to=m_btrfs@ml1.co.uk \
--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 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.