[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1231013856.7538.89.camel@think.oraclecorp.com>
Date: Sat, 03 Jan 2009 15:17:36 -0500
From: Chris Mason <chris.mason@...cle.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Matthew Wilcox <matthew@....cx>, Andi Kleen <andi@...stfloor.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-btrfs <linux-btrfs@...r.kernel.org>
Subject: Re: Btrfs for mainline
On Sat, 2009-01-03 at 14:50 -0500, Christoph Hellwig wrote:
> On Sat, Jan 03, 2009 at 12:17:06PM -0700, Matthew Wilcox wrote:
>
> > > - compat.h needs to go
> >
> > Later. It's still there for XFS.
>
> ?
> > > - there should be manpages for all the ioctls and other interfaces.
> >
> > I wonder if Michael Kerrisk has time to help with that. Cc'd.
>
> Actually a lot of the ioctl API don't just need documentation but
> a complete redo. That's true at least for the physical device
> management and subvolume / snaphot ones.
>
The ioctl interface is definitely not finalized. Adding more vs
replacing the existing ones is an open question.
> > > - various checkpath.pl level problems I think (e.g. printk levels)
> >
> > Can be fixed up later.
> >
> > > - the printks should all include which file system they refer to
> >
> > Ditto.
>
> >From painfull experience with a lot of things, including a filesystem
> you keep on mentioning it's clear that once stuff is upstream there
> is very little to no incentive to fix these things up.
>
I'd disagree here. Cleanup incentive is a mixture of the people
involved and the attention the project has.
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists