Re: linux-next: procedures

[Stephen Rothwell <sfr@canb.auug.org.au>]

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

Hi Randy,

On Tue, 18 Nov 2008 08:47:57 -0800 Randy Dunlap <randy.dunlap@oracle.com> wrote:
>
> > The following will cause a tree to be temporarily dropped from linux-next:
> > 	- non-trivial conflicts with Linus' tree
> > 	- build failures
> 
> One clarification, please.
> 
> Does this mean build failures that _you_ see/experience during tree merging
> and not other reported build failures?

Build failures I see during merging will cause the tree to be dropped
immediately (this forces me to not spend time trying to fix others
problems), other build failures may take a day or two before the
offending tree gets identified and dropped (but hopefully it will be
fixed before that happens).

A tree being dropped during merging does not imply fault - it may well be
a combination of trees that is the problem and I am always open to people
explaining things to me.  As long as we come up with a solution that I
can carry along.  However, most of the build failures I have seen so far
have been unexpected impact on other architectures/configs (than those
tested by the author), procedures gone wrong or carelessness ...

Trees do get picked up again at the next opportunity i.e. I still
fetch, inspect and attempt to merge "dropped" trees just in case people
don't get around to telling me they are fixed.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

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