From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: preparing a new xfsprogs release?
Date: Thu, 25 Aug 2011 02:23:16 -0400 [thread overview]
Message-ID: <20110825062316.GA17126@infradead.org> (raw)
In-Reply-To: <20110825061959.GN3162@dastard>
On Thu, Aug 25, 2011 at 04:19:59PM +1000, Dave Chinner wrote:
> On Thu, Aug 25, 2011 at 01:08:28AM -0400, Christoph Hellwig wrote:
> > We have the libxfs resync and a healthy amount of fixes in xfsprogs,
> > what about cutting a release in about 1-2 weeks from now?
>
> Probably a good idea.
>
> Once it is release, I'll look at doing another kernel code sync -
> this one will be a lot smaller than the last - and then we can start
> adding all the new stuff we've got on top of it...
I have a few things that I want to do to make syncs easier in the
future:
- stop using the plain xfs.h include in userland, and use the same
includes as in kernel space. This might require some new stub
headers and magic #include_next games in userland, but should really
ease our life there.
- split files only partially shared between kernel and userspace and
logical boundaries so that they can be shared 1:1. My poster child
for that would be to split a xfs_busy_extent.c out of xfs_alloc.c.
But let's get this release out before starting major surgery.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-08-25 6:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 5:08 preparing a new xfsprogs release? Christoph Hellwig
2011-08-25 6:19 ` Dave Chinner
2011-08-25 6:23 ` Christoph Hellwig [this message]
2011-08-25 7:09 ` Dave Chinner
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=20110825062316.GA17126@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--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