From: Joe Perches <joe@perches.com>
To: Patrick McHardy <kaber@trash.net>
Cc: Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: nf-next-2.6.git
Date: Tue, 28 Oct 2008 09:33:58 -0700 [thread overview]
Message-ID: <1225211639.5269.148.camel@localhost> (raw)
In-Reply-To: <49073E96.9000703@trash.net>
On Tue, 2008-10-28 at 17:32 +0100, Patrick McHardy wrote:
> Joe Perches wrote:
> > On Tue, 2008-10-28 at 13:26 +0100, Patrick McHardy wrote:
> >> Since Dave has created his net-next-2.6.git tree, I'm now also
> >> taking netfilter patches for 2.6.29. The nf-next-2.6.git tree
> >> is located at:
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/kaber/nf-next-2.6.git
> >
> > Should either or both of git trees be added to
> > MAINTAINERS: NETFILTER/IPTABLES/IPCHAINS?
> >
> > T: git.kernel.org/pub/scm/linux/kernel/git/kaber/nft-2.6.git
> > T: git.kernel.org/pub/scm/linux/kernel/git/kaber/nf-next-2.6.git
>
> The first one is a development tree for something not inside
> the kernel yet. Adding the second one would be fine.
I believe you got the order reversed.
This below could/should be added yes?
T: git.kernel.org/pub/scm/linux/kernel/git/kaber/nft-2.6.git
next prev parent reply other threads:[~2008-10-28 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 12:26 nf-next-2.6.git Patrick McHardy
2008-10-28 16:23 ` nf-next-2.6.git Joe Perches
2008-10-28 16:27 ` nf-next-2.6.git Jan Engelhardt
2008-10-28 16:29 ` nf-next-2.6.git Patrick McHardy
2008-10-28 16:32 ` nf-next-2.6.git Patrick McHardy
2008-10-28 16:33 ` Joe Perches [this message]
2008-10-28 16:36 ` nf-next-2.6.git Patrick McHardy
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=1225211639.5269.148.camel@localhost \
--to=joe@perches.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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).