linux-kernel - Re: [git pull] drm request 3

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]

Message-ID: <20100305122923.344e478e@lxorguk.ukuu.org.uk>
Date:	Fri, 5 Mar 2010 12:29:23 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Adam Jackson <ajax@...hat.com>,
	Matthew Garrett <mjg59@...f.ucam.org>,
	Dave Airlie <airlied@...ux.ie>, linux-kernel@...r.kernel.org,
	dri-devel@...ts.sf.net
Subject: Re: [git pull] drm request 3

> So man up, guys. Face the problem, rather than say "well, it's staging", 
> or "well, we can revert it". Neither of those really solve anything in the 
> short run _or_ the long run.

Linus stop and think for a minute instead. Maybe a timeline would help


		Nouveau development starts
		People ship highly experimental stuff for testers
		Code gets to the "works but really needs a clean up point"

		Linus demands it is merged
		Linus gets it merged as staging

		Developers start doing the cleanup

		Linus throws a tantrum because they did the cleanup after
		merge


*YOU* forced the early merge (rightly or wrongly)
*YOU* effectively created the API break problem

So blaming other people is quite out of order.

Alan
--
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/