From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id p7P79nug172381 for ; Thu, 25 Aug 2011 02:09:49 -0500 Received: from ipmail07.adl2.internode.on.net (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 6104B1132F0 for ; Thu, 25 Aug 2011 00:09:47 -0700 (PDT) Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [150.101.137.131]) by cuda.sgi.com with ESMTP id 4HbLjTcdPOqnjjfO for ; Thu, 25 Aug 2011 00:09:47 -0700 (PDT) Date: Thu, 25 Aug 2011 17:09:44 +1000 From: Dave Chinner Subject: Re: preparing a new xfsprogs release? Message-ID: <20110825070944.GP3162@dastard> References: <20110825050828.GA30775@infradead.org> <20110825061959.GN3162@dastard> <20110825062316.GA17126@infradead.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20110825062316.GA17126@infradead.org> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Christoph Hellwig Cc: xfs@oss.sgi.com On Thu, Aug 25, 2011 at 02:23:16AM -0400, Christoph Hellwig wrote: > 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. Yes, definitely. I think the changes to the dir2 headers will make things a lot easier in future, too, so further consolidation of the kernel headers along those would be a good thing to do as well. > But let's get this release out before starting major surgery. *nod* Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs