linux-kernel - Re: Announce: Linux-next (Or Andrew's dream :-))

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: <20080212.182012.153642549.davem@davemloft.net>
Date:	Tue, 12 Feb 2008 18:20:12 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	akpm@...ux-foundation.org
Cc:	torvalds@...ux-foundation.org, bfields@...ldses.org,
	jeff@...zik.org, linux-kernel@...r.kernel.org,
	linville@...driver.com
Subject: Re: Announce: Linux-next (Or Andrew's dream :-))

From: Andrew Morton <akpm@...ux-foundation.org>
Date: Tue, 12 Feb 2008 18:06:13 -0800

> So perhaps a better workflow would be keep the linux-next trees all
> messy, and then each developer can consolidate, rebase, join and
> drop things prior to sending their individual trees to Linus.

We could do that, but I believe Linus's main point is that if we go
and change the trees then in the end we're merging in something
different than what was actually tested, namely all the original trees
as merged into linux-next.

And I kind of agree with that.
--
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/