linux-kernel - Re: linux-next: manual merge of the msm tree with the arm tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 02 Feb 2011 19:15:32 -0500 (EST)
From:	Nicolas Pitre <nico@...xnic.net>
To:	David Brown <davidb@...eaurora.org>
Cc:	Greg KH <greg@...ah.com>, Russell King <rmk@....linux.org.uk>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>,
	Stepan Moskovchenko <stepanm@...eaurora.org>
Subject: Re: 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 http://ftp.arm.linux.org.uk/ 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 
HTTP.

Admitedly, if RMK had a public mirror on git.kernel.org 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.


Nicolas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/