From mboxrd@z Thu Jan  1 00:00:00 1970
From: hch@infradead.org (Christoph Hellwig)
Date: Sat, 22 Jan 2011 16:58:55 -0500
Subject: [PATCH 0/7] Nexus One Support
In-Reply-To: <AANLkTimKRCAVQSn8cic2OH2+2eOP+RKxWhUkpRw-B3k3@mail.gmail.com>
References: <1295632828.19880.22.camel@m0nster>
	<20110121100441.06a94482@jbarnes-desktop>
	<1295633882.19880.31.camel@m0nster>
	<AANLkTi=L+MW5-KLP_TKSxhstD8JEtBW=RKci5wSbZsd6@mail.gmail.com>
	<1295642995.19880.42.camel@m0nster>
	<AANLkTikVDn+W8t7KSym5tCGZowyYvoLFrk8d0mumiRF-@mail.gmail.com>
	<20110121234930.GK3043@thunk.org>
	<1295684398.19231.47.camel@jaguar>
	<20110122205535.GD8666@infradead.org>
	<AANLkTimKRCAVQSn8cic2OH2+2eOP+RKxWhUkpRw-B3k3@mail.gmail.com>
Message-ID: <20110122215855.GA22255@infradead.org>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org

On Sat, Jan 22, 2011 at 11:56:14PM +0200, Pekka Enberg wrote:
> We also tell people to submit crap into tree all the time - it's
> called staging!

Which is totally unrelated to this flameware.  Also if crap goes into
staging it doesn't go with years of useless version history.

>We also merge full history from time to time like in
> the case of btrfs.

We do it something, but only for projects that actually follow the Linux
commit guidelines.  

> Usually even "shitty git trees" have value in the history for people
> who're interested why the code is the way it is. But as people who
> actually looked at the patches, it doesn't apply here.

Thomas posted how the android tree commits looks.  How about getting a
clue before posting more useless noise in this thread?