| 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: <20080212.173817.111913348.davem@davemloft.net> Date: Tue, 12 Feb 2008 17:38:17 -0800 (PST) From: David Miller <davem@...emloft.net> To: torvalds@...ux-foundation.org Cc: bfields@...ldses.org, jeff@...zik.org, linux-kernel@...r.kernel.org, akpm@...ux-foundation.org, linville@...driver.com Subject: Re: Announce: Linux-next (Or Andrew's dream :-)) From: Linus Torvalds <torvalds@...ux-foundation.org> Date: Tue, 12 Feb 2008 17:31:10 -0800 (PST) > You don't see the problems as much, because you merge probably only > about a tenth of the volume I merge, and you can keep track of the > subsystem more. Good point. Now how do I remove a bogus commit for a tree that I've already pushed out and published for other people, without any record of it appearing in the GIT tree any more? How do I insert build fixes into existing changesets so that the tree is more bisectable? If Jeff merged in a tree that introduced a ton of whitespace errors git is complaing about, is there a way I can fixup that changeset in-place? (or should I tell Jeff to start adhering to GIT's whitespace warning messages when he applies patches?) Those are basically the major operations that would allow me to seriously consider rebasing a ton less often. -- 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