Re: linux-next: Requirements and process

[Stephen Rothwell]

On Fri, 2 May 2008 23:35:19 -0700 Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> On Sat, 3 May 2008 15:45:42 +1000 Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxx
http://www.canb.auug.org.au/~sfr/

Attachment: pgp00000.pgp
Description: PGP signature