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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 26 Oct 2009 22:18:54 -0700 (PDT)
From:	David Miller <>
Subject: Re: [RFC] to rebase or not to rebase on linux-next

From: Steven Rostedt <>
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
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists