[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20081119072455.e341b8e3.sfr@canb.auug.org.au>
Date: Wed, 19 Nov 2008 07:24:55 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Randy Dunlap <randy.dunlap@...cle.com>
Cc: linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus <torvalds@...ux-foundation.org>
Subject: Re: linux-next: procedures
Hi Randy,
On Tue, 18 Nov 2008 08:47:57 -0800 Randy Dunlap <randy.dunlap@...cle.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@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists