| 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: Sat, 10 Mar 2007 17:26:58 -0500 From: "michael chang" <thenewme91@...il.com> To: "Willy Tarreau" <w@....eu> Cc: "Stephen Clark" <Stephen.Clark@...lark.us>, "ck list" <ck@....kolivas.org>, "linux kernel mailing list" <linux-kernel@...r.kernel.org> Subject: Re: [ck] Re: RSDL v0.28 for 2.6.20 On 3/10/07, Willy Tarreau <w@....eu> wrote: > On Sat, Mar 10, 2007 at 04:56:57PM -0500, michael chang wrote: > > On 3/10/07, Willy Tarreau <w@....eu> wrote: > > >BTW, Con, I think that you should base your work on 2.6.20.[23] and not > > >2.6.20 next time, due to this conflict. It will get wider adoption. > ^^^^^^^^^^ > > > Maybe I'm naive, but I find this hard to understand -- 2.6.20.2 didn't > > exist when Con published his patch. (Con published it ~12 hours before > > the release of 2.6.20.2, from what I can tell.) How can he base his > > work on something that didn't yet exist? (And it applied cleanly to > > 2.6.20.1, the latest when he published it.) > > You see the words I have underlined ? "next time". I know for sure he > published it before 2.6.20.2, but now that it is out, I suggested that > Con rebases his work on this version for new releases. > Oh. That's my mistake, then. That makes sense. To me, it sounded like you were implying he was supposed to base it on 2.6.20.2 in advance, for some reason. *sigh* -- ~Mike - Just the crazy copy cat. - 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