From: Wang Shilong <wangshilong1991@gmail.com>
To: dsterba@suse.cz
Cc: Saul Wold <sgw@linux.intel.com>,
Chris Mason <chris.mason@fusionio.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Issue building a file based rootfs image with mkfs.btrfs
Date: Tue, 1 Oct 2013 22:56:56 +0800 [thread overview]
Message-ID: <AA924B80-FA15-4BF2-81EC-B24D335FDF45@gmail.com> (raw)
In-Reply-To: <20131001143556.GH18291@twin.jikos.cz>
> On Sat, Sep 28, 2013 at 10:51:54AM -0700, Saul Wold wrote:
>> On 09/28/2013 05:29 AM, Chris Mason wrote:
>> Ah great news! I want to verify is your git repo for btrfs-progs the main
>> upstream? I see loads of other patches flying around, but not applied
>> there.
>
> The patches land in the integration git repo
>
> http://repo.or.cz/w/btrfs-progs-unstable/devel.git
David no only did a great job in maintaining btrfs-progs but also helped a lot with us newbies towards btrfs world.
Anyway, i think we do need some necessary btrfs-progs update(for example some regression bug fixes)…
Thanks,
Wang
>
> at branches tagged by date.
> --
> 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:[~2013-10-01 14:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 18:19 Issue building a file based rootfs image with mkfs.btrfs Saul Wold
2013-09-22 18:28 ` Saul Wold
2013-09-28 12:29 ` Chris Mason
2013-09-28 17:51 ` Saul Wold
2013-10-01 14:35 ` David Sterba
2013-10-01 14:56 ` Wang Shilong [this message]
2013-10-01 20:50 ` Saul Wold
2013-10-02 1:18 ` Chris Mason
2013-10-14 15:25 ` Saul Wold
2013-10-14 15:26 ` Chris Mason
2013-10-14 20:51 ` 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=AA924B80-FA15-4BF2-81EC-B24D335FDF45@gmail.com \
--to=wangshilong1991@gmail.com \
--cc=chris.mason@fusionio.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=sgw@linux.intel.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).