Re: linux-next: Requirements and process

Re: linux-next: Requirements and process

[Randy Dunlap]

On Sat, 3 May 2008 16:07:24 +1000 Stephen Rothwell wrote:

> In case it isn't clear, I need to be told where I can get a particular
> tree from and who should be contacted in case of problems (I do not troll
> through the MAINTAINERS file).  I can currently handle git trees and
> quilt series.  I am willing to consider other formats/scms.  I also do
> not mind having multiple trees (or branches or series files) for a single
> subsystem/maintainer.
> 
> Series files must be annotated with an indication of the place in Linus'
> tree that they are based on using the following format:
> 
> # BASE <some identification of a place in Linus' tree>
> 
> This base can be a SHA1 or a release tag or one of the ...-git<n> or the
> output from "git describe".  Alternatively, you can be based on another
> tree in linux-next by using:
> 
> # NEXT_BASE <name of a tree in linux-next>

What do we use for BASE or NEXT_BASE if the base tree is linux-next?
Just don't use these annotations?


> The names are in the Next/Trees file in each release and normally do not
> change.
> 
> Also you may (if you like) delimit the parts of the series you want in
> linux-next by using:
> 
> # NEXT_PATCHES_START
> .
> .
> # NEXT_PATCHES_END
> 
> There can be multiple such sections.


---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/

Re: linux-next: Requirements and process

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]

Hi Randy,

On Tue, 22 Jul 2008 15:31:14 -0700 Randy Dunlap <randy.dunlap@oracle.com> wrote:
>
> > output from "git describe".  Alternatively, you can be based on another
> > tree in linux-next by using:
> > 
> > # NEXT_BASE <name of a tree in linux-next>
> 
> What do we use for BASE or NEXT_BASE if the base tree is linux-next?
> Just don't use these annotations?

The name from the Next/Trees file in any linux-next release.  You should
be very careful doing this if you don't control the other tree, though.
And you should let me know so that I can order the trees appropriately.

This was mainly added for Greg who has 4 quilt series in linux-next that
depend on each other.  If you depend on some random tree that changes day
to day your quilt series may no longer apply cleanly on top of it.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: linux-next: Requirements and process

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 823 bytes --]

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.
> 
> Except for m68knommu, which pops unexpectedly out of the woodwork during
> the merge window.  I've asked that this be altered ;)

So (from the above list) cris, m68knommu and mips have joined the
linux-next fray ...

(cc's some maintainers)
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]