[lkml]   [2005]   [Jan]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] add feature-removal-schedule.txt documentation
    On Fri, Jan 07, 2005 at 12:23:35AM +0000, Christoph Hellwig wrote:
    > On Thu, Jan 06, 2005 at 03:56:34PM -0800, Greg KH wrote:
    > > On Thu, Jan 06, 2005 at 03:26:21PM -0800, Andrew Morton wrote:
    > > > Which begs the question "how do we ever get rid of these things when we
    > > > have no projected date for Linux-2.8"?
    > > >
    > > > I'd propose:
    > > >
    > > > a) Create Documentation/feature-removal-schedule.txt which describes
    > > > things which are going away, when, why, who is involved, etc.
    > >
    > > Ok, I'll bite, here's a patch that does just that. Look good?
    > another item:
    > What: unused exports that don't make sense as general APIs
    > When: as soon as noticed
    > Files: all
    > Why: Unused functions bloat the kernel and wrong exported functions
    > will make external driver authors write code that's buggy and
    > unmaintainable.
    > Who: Christoph Hellwig <> & others.

    Heh, yeah right, might as well just add the following also if we are in
    the CYA mode:

    What: Broken function parameters and entire functions
    When: As soon as noticed
    Files: All
    Why: See Documentation/stable_api_nonesense.txt for why this is
    Who: Greg Kroah-Hartman <> and others.

    But I think this file is for specific things, the above, and your entry,
    shouldn't be needed. Well, I would hope so, but odds are it might be
    necessary just to keep from answering the same questions all the time...


    greg k-h

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:09    [W:0.020 / U:4.588 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site