All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Green <cmg@dok.org>
To: netfilter-devel@lists.netfilter.org
Subject: Re: Logging NAT translations?
Date: Mon, 02 Aug 2004 11:16:43 -0400	[thread overview]
Message-ID: <87r7qpzi1w.fsf@ion.xlipstream.com> (raw)
In-Reply-To: <20040801170153.GC14539@sunbeam2> (Harald Welte's message of "Sun, 1 Aug 2004 19:01:53 +0200")

[-- Attachment #1: Type: text/plain, Size: 831 bytes --]

Harald Welte <laforge@netfilter.org> writes:

> then someone needs to do some porting/merging work... patches
> appreciated ;)

Ok... I'm happy to work on it if I can get some pointers on where/how
development should happen.

I'm guessing HEAD iptables, HEAD patch-o-matic-ng, linux-2.6.7?

The requirements hierarchy is a pain for me to figure out. Shouldn't
be too bad to generate a graphviz digraph for it though.

For POM-NG, should I be doing:

./runme pending
./runme nfnetlink-ctnetlink-0.13

or should I walk through the deps in nfnetlink-ctnetlink-0.13/info,
apply/fix all of those patches recursively.

For fixing a single patch, what should the .orig tree be? The tree
with all dependencies applied?

Any guidance on tree mangagement would be appreciated.

Thanks,
Chris
-- 
Chris Green <cmg@dok.org>
Chicken's thinkin'

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2004-08-02 15:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28 21:07 Logging NAT translations? Chris Green
2004-08-01 17:01 ` Harald Welte
2004-08-02 15:16   ` Chris Green [this message]
2004-08-02 15:42     ` Chris Green
2004-08-02 16:11   ` Sven Schuster
2004-08-02 17:13     ` Harald Welte
     [not found]       ` <20040802180031.GA22839@zion.homelinux.com>
2004-08-03 15:10         ` Sven Schuster

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=87r7qpzi1w.fsf@ion.xlipstream.com \
    --to=cmg@dok.org \
    --cc=netfilter-devel@lists.netfilter.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.