[Ksummit-2012-discuss] [ATTEND] structuring of tools et.al and linux-devel.git repo

Konrad Rzeszutek Wilk konrad at darnok.org
Tue Jun 19 22:39:35 UTC 2012

On Tue, Jun 19, 2012 at 2:21 PM, Steven Rostedt <rostedt at goodmis.org> wrote:
> On Tue, 2012-06-19 at 14:10 -0400, Konrad Rzeszutek Wilk wrote:
>> > 2) Creating a linux-devel.git repo
>> >
>> > Some of the discussion so far has been about code getting into Linus's
>> > tree without going through linux-next. Or changing between the two. I
>> > would like to suggest adding a linux-devel.git repo that would let
>> > anyone that requests to add their development code to this repo. It may
>> > even spot duplicate work that is going on, or a place to house competing
>> > projects where it will be easier to do comparisons.
>> >
>> > If a pull causes the build to break or to break others code, then it
>> > will be reverted (not pulled), and a nasty email will be sent to the
>> > maintainer to fix it.
>> I like this... Is it also possible to add automatic cross builds
>> so the offending maintainer gets an email so she/he can fix it up?
> Yes, very easily done with ktest. Take a look at (in 3.5-rc):
>   tools/testing/ktest/examples/crosstests.conf

I was thinking more of some system doing it - that way it would be
doing it for everybody.

More information about the Ksummit-2012-discuss mailing list