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: Fri, 18 Jul 2014 00:32:31 +0200 (CEST) From: Thomas Gleixner <tglx@...utronix.de> To: LKML <linux-kernel@...r.kernel.org> cc: John Stultz <john.stultz@...aro.org>, Peter Zijlstra <peterz@...radead.org> Subject: Re: [patch V2 00/64] timekeeping: 2038, optimizations, NMI safe accessors On Wed, 16 Jul 2014, Thomas Gleixner wrote: > The series is against tip/timers/core. It's also available in git at: > > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tglx/timers/core Anyone, who pulled from there, please do again. I just got aware that the branch was stale. I could swear that I updated it and according to my bash history I really did a force push on that branch and a verify that origin/tglx/timers/core is the same as tglx/timers/core, that's the same procedure I use before sending out a pull request to Linus - got burned once not doing that :) The same thing happened about half a year ago, and looking at the mail thread it was also a forced update, i.e. git push -f I'm not blaming anyone except me as long as I can't be sure that my scripting around git is not to blame. Sorry for the inconveniance! Thanks, tglx -- 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