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
| ||
|
Message-ID: <4AE741CE.6050200@s5r6.in-berlin.de> Date: Tue, 27 Oct 2009 19:54:06 +0100 From: Stefan Richter <stefanr@...6.in-berlin.de> To: Theodore Tso <tytso@....edu> CC: "Luck, Tony" <tony.luck@...el.com>, Ingo Molnar <mingo@...e.hu>, Steven Rostedt <rostedt@...dmis.org>, LKML <linux-kernel@...r.kernel.org>, Nicolas Pitre <nico@...xnic.net>, Stephen Rothwell <sfr@...b.auug.org.au>, "Luis R. Rodriguez" <mcgrof@...il.com>, Jeff Garzik <jeff@...zik.org>, Robert Richter <robert.richter@....com>, Dmitry Torokhov <dmitry.torokhov@...il.com>, Jean Delvare <khali@...ux-fr.org>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [RFC] to rebase or not to rebase on linux-next On 10/27/2009 7:07 PM, Theodore Tso wrote: > On Mon, Oct 26, 2009 at 07:01:57PM +0100, Stefan Richter wrote: >> A missing >> allocation failure check or a missing tracepoint don't break >> bisectability. So why discard this history? (It was already published >> in a release preview.) > > There are multiple issues for rewinding patches. One is to avoid > breaking bisectability. Other is to keep related changes in > functionality in a single place. 2-3 years for now, does anyone > really care about retaining development history? In the human memory, > one of the most important parts of long-term memory formation is > *forgetting*; that is, editing down everything that happened down to > the most cogent and importants bits of history. [...] Sure. But when is the deadline for doing this? The evening before you send a pull request to Linus? Or already when you commit to the branch from which Stephen pulls into linux-next, which means: This is code and history which I would ask Linus to pull right now if he was in merge mode today. [I for one would indeed add non-essential credits or otherwise touch up the history even if it already was in linux-next but Linus' next merge window isn't there yet. But I would batch such rewinds up for a single occasion between merge windows, and only do them at all if there are several such changes to make it worthwhile. And I only do that because I work at driver code with limited interaction with other subsystems, and virtually no co-developers in the project.] -- Stefan Richter -=====-==--= =-=- ==-== http://arcgraph.de/sr/ -- 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/
Powered by blists - more mailing lists