linux-kernel - Re: [PATCH 0/7] Nexus One Support

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:	Sat, 22 Jan 2011 23:56:14 +0200
From:	Pekka Enberg <penberg@...nel.org>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	"Ted Ts'o" <tytso@....edu>, Daniel Walker <dwalker@...eaurora.org>,
	Dima Zavin <dmitriyz@...gle.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Joe Perches <joe@...ches.com>, linux-arm-msm@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	davidb@...eaurora.org
Subject: Re: [PATCH 0/7] Nexus One Support

Hi Christoph!

On Sat, Jan 22, 2011 at 10:19:58AM +0200, Pekka Enberg wrote:
>> Sure, it would have been nicer for everyone involved if Daniel would
>> have kept the original patches and added new patches to clean it up on
>> top of that to preserve the history.

On Sat, Jan 22, 2011 at 10:55 PM, Christoph Hellwig <hch@...radead.org> wrote:
> No, it would be a complete fucking mess that way.  We tell people to
> submit standalone and well formed patches all the time.  Why would it
> make any difference just because they were also commited to a shitty git
> tree somewhere else?

We also tell people to submit crap into tree all the time - it's
called staging! We also merge full history from time to time like in
the case of btrfs.

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.

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