preparing a new xfsprogs release?

preparing a new xfsprogs release?

[Christoph Hellwig]

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?

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: preparing a new xfsprogs release?

[Dave Chinner]

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...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: preparing a new xfsprogs release?

[Christoph Hellwig]

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

Re: preparing a new xfsprogs release?

[Dave Chinner]

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