| 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
| ||
|
Date: Fri, 01 Mar 2013 23:22:58 -0500 From: Steven Rostedt <rostedt@...dmis.org> To: Stephen Rothwell <sfr@...b.auug.org.au> Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: linux-next: build failure after merge of the ftrace tree On Sat, 2013-03-02 at 15:17 +1100, Stephen Rothwell wrote: > > > I made some major changes and wanted testing on it as soon as possible. > > I've done tons of testing on my own but I wanted a broader audience. Do > > you want me to pull my tree and reset it to what is only for 3.9? > > Yes, please. The reasoning is that until -rc1 is out we don't want to > complicate life for people whose code has not yet been merged by > reporting problems in code that will not be merged until the next merge > window. OK, I reset it to what I based my work on, and that commit is in Linus's tree. > > That is why my daily reports during the merge window start with: > > "Please do not add any work destined for v3.10 to your -next included > branches until after Linus has release v3.9-rc1." > > But I am beginning to realise that not many actually read those reports (I /me is guilty :-( > had the date wrong on two of them this week and it was only noticed after > the second one :-(). > I'm try to be better next time. -- Steve -- 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