<p><br>
><br>
> 2) Creating a linux-devel.git repo<br>
><br>
> Some of the discussion so far has been about code getting into Linus's<br>
> tree without going through linux-next. Or changing between the two. I<br>
> would like to suggest adding a linux-devel.git repo that would let<br>
> anyone that requests to add their development code to this repo. It may<br>
> even spot duplicate work that is going on, or a place to house competing<br>
> projects where it will be easier to do comparisons.<br>
><br>
> If a pull causes the build to break or to break others code, then it<br>
> will be reverted (not pulled), and a nasty email will be sent to the<br>
> maintainer to fix it.<br>
><br>
> Rebases will be allowed, and even encouraged. No one should be basing<br>
> their work off of this tree, but they can use this tree to test their<br>
> work against other development code. I want this to be like the old -mm<br>
> tree was.<br>
><br>
> When your code has been vetted by the linux-devel repo, you can then<br>
> push it to the linux-next repo. Ideally, your code will be good enough<br>
> that it would no longer need to be rebased when it gets there, and the<br>
> linux-next code will be ready for Linus to pull.<br>
><br>
> I believe a repo like this will get new development code more exposure<br>
> and may even find bugs before it gets to the linux-next stage. Maybe<br>
> even give better review. If a developer notices something different<br>
> (good or bad) with how their system is working, if they can spot the<br>
> cause it can be reported to the maintainer of the developmental work.<br>
> This will leave less surprises when code goes mainline.<br>
></p>
<p>What I would be interested in knowing is if someone might be interested in generating this tree, do we have a list of branches maintainers/developers want to push right away available somewhere?</p>
<p>Dhaval </p>