From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH TARBALL, DEV ONLY] xfsprogs: metadata CRC support V2
Date: Mon, 29 Apr 2013 11:46:00 +1000 [thread overview]
Message-ID: <20130429014600.GZ10481@dastard> (raw)
In-Reply-To: <20130426061231.GA8338@infradead.org>
On Fri, Apr 26, 2013 at 02:12:31AM -0400, Christoph Hellwig wrote:
> Can you send out the libxfs resync separately? I think that's something
> that should go in ASAP.
Yes, the next version of the tarball will be split up into 3 parts:
1. - remove dirv1
- libxfs kernel resync
- add CRC infrstructure
- libxlog kernel resync
2. add CRC support to libxfs
3. Add CRC support to mkfs, repair, db, etc....
The plan is to do the resync (part 1) as soon as the current
xfsprogs RC is officially released as that gets the largest part of
the patchset into the upstream tree. I've already got this part of
it pretty much ready to go....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-04-29 1:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 14:55 [PATCH TARBALL, DEV ONLY] xfsprogs: metadata CRC support V2 Dave Chinner
2013-04-25 16:37 ` Mark Tinguely
2013-04-25 21:39 ` Dave Chinner
2013-04-25 21:12 ` Mark Tinguely
2013-04-25 21:40 ` Dave Chinner
2013-04-29 21:33 ` Mark Tinguely
2013-04-29 22:09 ` Dave Chinner
2013-04-30 12:03 ` Dave Chinner
2013-04-26 6:12 ` Christoph Hellwig
2013-04-29 1:46 ` Dave Chinner [this message]
2013-05-09 12:42 ` Rich Johnston
2013-05-09 13:22 ` Dave Chinner
2013-05-09 13:37 ` Rich Johnston
2013-05-09 13:41 ` Rich Johnston
2013-05-09 20:24 ` Rich Johnston
2013-05-09 22:35 ` Dave Chinner
2013-05-09 23:00 ` Rich Johnston
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=20130429014600.GZ10481@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.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