| 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, 15 Aug 2008 23:39:15 +0200 From: "Julius Volz" <juliusv@...gle.com> To: "David Miller" <davem@...emloft.net> Cc: horms@...ge.net.au, lvs-devel@...r.kernel.org, netdev@...r.kernel.org, sven.wegener@...aler.net, wensong@...ux-vs.org, ja@....bg Subject: Re: [GIT] Please pull updates for IPVS On Fri, Aug 15, 2008 at 11:18 PM, David Miller <davem@...emloft.net> wrote: > From: "Julius Volz" <juliusv@...gle.com> > Date: Fri, 15 Aug 2008 13:31:59 +0200 > >> On Fri, Aug 15, 2008 at 3:02 AM, Simon Horman <horms@...ge.net.au> wrote: >> > thanks for the clarification. In that case I believe that >> > all of these changes can wait. >> >> Ok, how does the process work? Do I send the patches again at a later >> point or will they be pulled from your tree then? > > Simon can maintain a tree if he wants, and your feature patches can > go into there. > > Later when I start accepting net-next-2.6 stuff, I can pull things in > from him. > > Or Sven can maintain such a GIT tree, whoever wants to do it. Ok, thanks! Sorry, I was not fully aware about the process and what may go in when. From reading about it, it seems that after an -rc1, only bug fixes are accepted until after the stable release. So I guess you only start accepting net-next-2.6 stuff after the official stable release, too? Julius -- Google Switzerland GmbH -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists