From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: IPSEC maintainership...
Date: Tue, 16 Oct 2012 08:21:54 +0200 [thread overview]
Message-ID: <20121016062154.GG21577@secunet.com> (raw)
In-Reply-To: <20121016.021435.220828722592000976.davem@davemloft.net>
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.
next prev parent reply other threads:[~2012-10-16 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 17:38 IPSEC maintainership David Miller
2012-10-16 6:11 ` Steffen Klassert
2012-10-16 6:14 ` David Miller
2012-10-16 6:21 ` Steffen Klassert [this message]
2012-10-17 9:13 ` Steffen Klassert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121016062154.GG21577@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).