From: Patrick McHardy <kaber@trash.net>
To: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Subject: Re: netfilter git trees
Date: Wed, 18 Feb 2009 16:39:45 +0100 [thread overview]
Message-ID: <499C2BC1.6090502@trash.net> (raw)
In-Reply-To: <499C2B19.9090307@trash.net>
Patrick McHardy wrote:
> Just FYI, I've created two new netfilter trees based on Dave's
> suggestions and moved the queued commits over. The nf-2.6.git
> tree should still have a linear history, the nf-next-2.6.git
> tree might not.
Crap, and I messed it up by applying an old version of a patch
from Jan :)
Should be fixed shortly.
prev parent reply other threads:[~2009-02-18 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 15:36 netfilter git trees Patrick McHardy
2009-02-18 15:39 ` Patrick McHardy [this message]
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=499C2BC1.6090502@trash.net \
--to=kaber@trash.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.