| 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: Mon, 13 Oct 2008 11:23:09 -0700 (PDT) From: David Miller <davem@...emloft.net> To: khc@...waw.pl Cc: bunk@...nel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: Please pull - generic HDLC From: Krzysztof Halasa <khc@...waw.pl> Date: Mon, 13 Oct 2008 16:53:17 +0200 > Adrian Bunk <bunk@...nel.org> writes: > > > The over 3 weeks old -next already contains mostly the same as the HDLC > > tree contains now. > > > > The thing you two should sort out is why the tree ended up as an own > > tree in -next instead of pull requests to David long ago. > > > > E.g. the netdev and wireless trees also don't go into -next, but instead > > with frequent pull requests to David. > > I can't see any problem with this, is there any? > > I want the HDLC tree tested in next before it's merged upstream > (= David's tree(s)). I don't want to push crap upstream first and > only then try to fix it (though a bug still slips in sometimes). You're supposed to have your changes merged into the relevant subsystem tree long before Linus's merge window opens up. That's how it is meant to work. What I'm doing with networking is nothing special. So please be punctual and merge early and often to Jeff and myself, so that you don't miss the merge window in the future. -- 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