From: cwillu <cwillu@cwillu.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: "open_ctree failed", unable to mount the fs
Date: Fri, 7 Jan 2011 14:18:47 -0600 [thread overview]
Message-ID: <AANLkTimpci_RHZ2p82DfKCP3n1DBtRVVj+yQzC7v4EWb@mail.gmail.com> (raw)
In-Reply-To: <4D27711B.4090606@wpkg.org>
On Fri, Jan 7, 2011 at 2:01 PM, Tomasz Chmielewski <mangoo@wpkg.org> wr=
ote:
> On 07.01.2011 20:46, cwillu wrote:
>
>>> However, I don't see the tool when I clone the latest git - am I mi=
ssing
>>> something?
>>
>> It's not built by the makefile by default; =A0"make btrfs-select-sup=
er"
>> as stated above will make it.
>
> $ grep select Makefile
> $ grep super Makefile
> $ grep -r select-super *
> $ grep -r selects-super *
>
>
> I used:
>
> git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs-unsta=
ble.git
> next
You checked out the master branch into a folder called next. "-b
next" is the option to checkout a specific branch. From your existing
checkout, "git checkout -t origin/next" will switch to that branch.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-01-07 20:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 19:25 "open_ctree failed", unable to mount the fs Tomasz Chmielewski
2011-01-07 19:47 ` cwillu
[not found] ` <AANLkTik3GZVTwco+4PNFriB0+t_U=e+dH0UOgK_3P9D5@mail.gmail.com>
2011-01-07 20:01 ` Tomasz Chmielewski
2011-01-07 20:18 ` cwillu [this message]
2011-01-07 20:44 ` Tomasz Chmielewski
[not found] <S1750921Ab1CIXPz/20110309231555Z+1799@vger.kernel.org>
2011-03-09 23:28 ` Tomáš Thiemel
-- strict thread matches above, loose matches on Subject: below --
2011-01-07 19:01 Tomasz Chmielewski
2011-01-07 19:09 ` Hugo Mills
2011-01-07 20:02 ` 'open_ctree failed', " Ken D'Ambrosio
2011-01-07 20:31 ` cwillu
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=AANLkTimpci_RHZ2p82DfKCP3n1DBtRVVj+yQzC7v4EWb@mail.gmail.com \
--to=cwillu@cwillu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mangoo@wpkg.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 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).