lkml.org 
[lkml]   [2008]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: linux-next: Requirements and process
    On Fri, 2 May 2008 23:35:19 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
    >
    > On Sat, 3 May 2008 15:45:42 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
    >
    > > The following architectures are not in linux-next (and should be):
    > >
    > > alpha cris frv
    > > h8300 m32r m68knommu
    > > mips mn10300 parisc
    > > um v850 xtensa
    >
    > mips, m32r, parisc and xtensa do have git trees. The rest are mastered as
    > discrete patches in -mm.

    So, I was wondering if it would be worth while having subsections to a
    series file like:

    # NEXT_PATCHES_START [<label> [<base>]]

    # NEXT_PATCHES_END

    With <label> sections being logically separate enough that we can talk
    about them/drop them/merge them at different places etc.

    Or am I over engineering? :-)

    > Except for m68knommu, which pops unexpectedly out of the woodwork during
    > the merge window. I've asked that this be altered ;)

    Yeah, I saw that, thanks.

    --
    Cheers,
    Stephen Rothwell sfr@canb.auug.org.au
    http://www.canb.auug.org.au/~sfr/
    [unhandled content-type:application/pgp-signature]
    \
     
     \ /
      Last update: 2008-05-03 09:49    [W:0.046 / U:0.084 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site