From: Mark Fasheh <mfasheh@suse.de>
To: Anand Jain <Anand.Jain@oracle.com>
Cc: chris.mason@fusionio.com, linux-btrfs@vger.kernel.org,
ablock84@googlemail.com
Subject: Re: [PATCH 2/3] btrfs-progs: libify some parts of btrfs-progs
Date: Mon, 14 Jan 2013 10:16:43 -0800 [thread overview]
Message-ID: <20130114181643.GR12558@wotan.suse.de> (raw)
In-Reply-To: <50F37E8D.3070107@oracle.com>
On Mon, Jan 14, 2013 at 11:42:05AM +0800, Anand Jain wrote:
>
>
> Mark,
>
> Its bit strange, the steps given before can reproduce
> the problem still on my older workspace. However when
> I try with the fresh clone, it can reproduce the issue
> (4 times, consistently) only with the following (new)
> steps..
Ok.
> # git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git
>
> # cd btrfs-progs/
> # make version; make install
Ahh, this *does* reproduce for me. I think we just need to add libbtrfs as a
target somewhere. I'll fix it up. Thanks so much for drilling down to a test
case!
--Mark
--
Mark Fasheh
next prev parent reply other threads:[~2013-01-14 18:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 21:41 [PATCH 0/3] btrfs-progs: better support for external users of send Mark Fasheh
2013-01-08 21:41 ` [PATCH 1/3] btrfs-progs: Add support for BTRFS_SEND_FLAG_NO_FILE_DATA Mark Fasheh
2013-01-08 21:41 ` [PATCH 2/3] btrfs-progs: libify some parts of btrfs-progs Mark Fasheh
2013-01-11 9:31 ` Anand Jain
2013-01-11 23:00 ` Mark Fasheh
2013-01-14 3:42 ` Anand Jain
2013-01-14 18:16 ` Mark Fasheh [this message]
2013-01-14 22:27 ` Mark Fasheh
2013-01-14 3:43 ` Anand Jain
2013-01-14 18:10 ` Mark Fasheh
2013-01-15 8:06 ` Anand Jain
2013-01-16 22:11 ` Mark Fasheh
2013-01-14 14:18 ` Arvin Schnell
2013-01-14 18:14 ` Mark Fasheh
2013-01-14 22:26 ` Arvin Schnell
2013-01-15 12:46 ` Ilya Dryomov
2013-01-15 13:26 ` Arvin Schnell
2013-01-08 21:41 ` [PATCH 3/3] btrfs-progs: add send-test Mark Fasheh
2013-01-11 9:28 ` Anand Jain
2013-01-11 23:02 ` Mark Fasheh
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=20130114181643.GR12558@wotan.suse.de \
--to=mfasheh@suse.de \
--cc=Anand.Jain@oracle.com \
--cc=ablock84@googlemail.com \
--cc=chris.mason@fusionio.com \
--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 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).