From: liubo <liubo2009@cn.fujitsu.com>
To: Jan Schmidt <list.btrfs@jan-o-sch.net>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Backref walking utilities
Date: Thu, 26 May 2011 09:51:25 +0800 [thread overview]
Message-ID: <4DDDB21D.6040904@cn.fujitsu.com> (raw)
In-Reply-To: <4DDD1B7A.4090709@jan-o-sch.net>
On 05/25/2011 11:08 PM, Jan Schmidt wrote:
> On 05/23/2011 12:02 PM, Arne Jansen wrote:
>> Hi liubo,
>>
>> On 23.05.2011 11:53, liubo wrote:
>>> As one of my plans, I'm going to take this project over unless someone has been working on it.
>> Jan Schmidt has a patch for scrub nearly ready, that does some
>> ref-walking to report affected files to the user. While this is
>> kernel code and you're planning to add user-space code, it might
>> still be possible to share some of it. Maybe the efforts can be
>> coordinated.
>
> The patches are ready and should be flexible enough to use for your
> purpose. However I use them in context of the scrub code, thus I'm
> planning to send them out as soon as the current version of scrub is
> included in Chris' master.
>
> If anybody wants to test the patches before that (apply well against
> Arnes scrub branch), drop me an email.
>
I'd like to have a look ahead. Would you please give the address of these patches?
thanks,
liubo
> -Jan
> --
> 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
>
prev parent reply other threads:[~2011-05-26 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 9:53 Backref walking utilities liubo
2011-05-23 10:02 ` Arne Jansen
2011-05-23 10:15 ` Hugo Mills
2011-05-25 15:08 ` Jan Schmidt
2011-05-26 1:51 ` liubo [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=4DDDB21D.6040904@cn.fujitsu.com \
--to=liubo2009@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
/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).