From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steffen Klassert <steffen.klassert@secunet.com>
Subject: Re: IPSEC maintainership...
Date: Tue, 16 Oct 2012 08:21:54 +0200
Message-ID: <20121016062154.GG21577@secunet.com>
References: <20121015.133833.2211899390966002142.davem@davemloft.net>
 <20121016061154.GF21577@secunet.com>
 <20121016.021435.220828722592000976.davem@davemloft.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8BIT
Cc: netdev@vger.kernel.org, herbert@gondor.apana.org.au
To: David Miller <davem@davemloft.net>
Return-path: <netdev-owner@vger.kernel.org>
Received: from a.mx.secunet.com ([195.81.216.161]:33426 "EHLO a.mx.secunet.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751459Ab2JPGV6 convert rfc822-to-8bit (ORCPT
	<rfc822;netdev@vger.kernel.org>); Tue, 16 Oct 2012 02:21:58 -0400
Content-Disposition: inline
In-Reply-To: <20121016.021435.220828722592000976.davem@davemloft.net>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On Tue, Oct 16, 2012 at 02:14:35AM -0400, David Miller wrote:
> 
> If you want you can maintainer an IPSEC GIT tree, where you apply any
> submitted IPSEC changes.
> 
> Once you are satisfied with their quality and they pass your tests,
> you simply send me a formal GIT pull request just like any other
> networking subsystem (netfilter, wireless, etc.) currently does.

Sounds good, let's do it this way. I'll set up a git tree and
process the incomming IPsec patches.