[lkml]   [2011]   [Feb]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: linux-next: manual merge of the msm tree with the arm tree
On Wed, 2 Feb 2011, David Brown wrote:

> On Wed, Feb 02 2011, Nicolas Pitre wrote:
> > The actual problem here is that some people, notably the msm folks, are
> > bypassing the maintainer hierarchy and going straight to Linus for their
> > pull requests instead of asking RMK to pull. We once debated this at
> > some point and it was agreed that completely independent SOC specific
> > code with no dependencies on the common ARM code _could_ go straight to
> > Linus directly if they crave for it.
> I also have no real problem sending pull requests to RMK instead of
> Linus, as long as it isn't a pain. Linus gives clear directions as to
> how his tree works, and when he expects what kinds of pull requests.
> Weird web-based patch tracking systems are a pain. Pull requests from
> git with a fairly easy way to know when they've been pulled are not.

RMK accepts pull requests. He also stated pretty clearly when he wishes
for those requests to happen, or rather when it is too late for those
requests to come by so he has a chance to sort his tree out in time for
the merge window.

> I also find that is frequently
> inaccessable, and usually slow.

The "slow" part should be fixed now that the Git server over there has
been configured to serve Git requests using the Git smart protocol over

Admitedly, if RMK had a public mirror on that would help
things (a lot of people do have rebasing Git repos there already).

> As it stands, so far, it's been a lot less work for me to send directly
> to Linus, and resolve the issues that come up when they do.

This is however more work for Linus who already expressed some concerns
about too many people going to him directly while he'd prefer a more
distributed flow.


 \ /
  Last update: 2011-02-03 01:17    [W:0.057 / U:13.088 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site