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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 26 Oct 2009 22:18:54 -0700 (PDT) From: David Miller <davem@...emloft.net> To: rostedt@...dmis.org Cc: sam@...nborg.org, mingo@...e.hu, linux-kernel@...r.kernel.org, nico@...xnic.net, tony.luck@...el.com, sfr@...b.auug.org.au, mcgrof@...il.com, jeff@...zik.org, robert.richter@....com, dmitry.torokhov@...il.com, khali@...ux-fr.org, torvalds@...ux-foundation.org Subject: Re: [RFC] to rebase or not to rebase on linux-next From: Steven Rostedt <rostedt@...dmis.org> Date: Mon, 26 Oct 2009 23:02:38 -0400 > Whether I'm sending a patch to Ingo, Linus, Andrew, or even you, I would > do it publicly and have a git repo to pull from for simplicity. Sure, but just don't do it with a GIT repo that's going to make it's way to Linus. When you commit to any such GIT repo, you're making a permanent irrevocable change whose history cannot be changed. And given what you get in return for that, it's a pretty reasonable constraint. -- 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