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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080815.141841.268348002.davem@davemloft.net>
Date:	Fri, 15 Aug 2008 14:18:41 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	juliusv@...gle.com
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

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.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ