From: Max Kellermann <max@duempel.org>
To: netfilter-devel@lists.netfilter.org
Cc: Robert Iakobashvili <roberti@GoNetworks.com>
Subject: Re: [PATCH pom-ng 2/5] author update
Date: Wed, 19 Jan 2005 01:46:11 +0100 [thread overview]
Message-ID: <20050119004611.GD12967@roonstrasse.net> (raw)
In-Reply-To: <20050119004513.GB12967@roonstrasse.net>
[-- Attachment #1: Type: text/plain, Size: 128 bytes --]
On 2005/01/19 01:45, Max Kellermann <max@duempel.org> wrote:
> add myself as module author
oh no, the patchfile was missing.
[-- Attachment #2: 02-update_author.patch --]
[-- Type: text/plain, Size: 1886 bytes --]
Wed Jan 19 01:32:02 CET 2005 max@duempel.org
* added new author
diff -rN -u h323-3-old/h323-conntrack-nat/info h323-3-new/h323-conntrack-nat/info
--- h323-3-old/h323-conntrack-nat/info 2005-01-19 01:35:42.916373424 +0100
+++ h323-3-new/h323-conntrack-nat/info 2005-01-19 01:31:51.000000000 +0100
@@ -1,4 +1,4 @@
-Author: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
+Author: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>, Max Kellermann <max@duempel.org>
Status: Alpha
Repository: extra
Requires: linux >= 2.6.10-mm2
diff -rN -u h323-3-old/h323-conntrack-nat/linux/net/ipv4/netfilter/ip_conntrack_h323.c h323-3-new/h323-conntrack-nat/linux/net/ipv4/netfilter/ip_conntrack_h323.c
--- h323-3-old/h323-conntrack-nat/linux/net/ipv4/netfilter/ip_conntrack_h323.c 2005-01-19 01:35:42.916373424 +0100
+++ h323-3-new/h323-conntrack-nat/linux/net/ipv4/netfilter/ip_conntrack_h323.c 2005-01-19 01:35:42.963366280 +0100
@@ -1,6 +1,7 @@
/*
* H.323 'brute force' extension for H.323 connection tracking.
* Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
+ * (c) 2005 Max Kellermann <max@duempel.org>
*
* Based on ip_masq_h323.c for 2.2 kernels from CoRiTel, Sofia project.
* (http://www.coritel.it/projects/sofia/nat/)
diff -rN -u h323-3-old/h323-conntrack-nat/linux/net/ipv4/netfilter/ip_nat_h323.c h323-3-new/h323-conntrack-nat/linux/net/ipv4/netfilter/ip_nat_h323.c
--- h323-3-old/h323-conntrack-nat/linux/net/ipv4/netfilter/ip_nat_h323.c 2005-01-19 01:35:42.914373728 +0100
+++ h323-3-new/h323-conntrack-nat/linux/net/ipv4/netfilter/ip_nat_h323.c 2005-01-19 01:35:42.961366584 +0100
@@ -1,6 +1,7 @@
/*
* H.323 'brute force' extension for NAT alteration.
* Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
+ * (c) 2005 Max Kellermann <max@duempel.org>
*
* Based on ip_masq_h323.c for 2.2 kernels from CoRiTel, Sofia project.
* (http://www.coritel.it/projects/sofia/nat.html)
next prev parent reply other threads:[~2005-01-19 0:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 0:43 [PATCH pom-ng 0/5] RFC: ip_nat|conntrack_h323.c on 2.6, first preview Max Kellermann
2005-01-19 0:44 ` [PATCH pom-ng 1/5] update kernel requires Max Kellermann
2005-01-19 0:45 ` [PATCH pom-ng 2/5] author update Max Kellermann
2005-01-19 0:46 ` Max Kellermann [this message]
2005-01-19 0:45 ` [PATCH pom-ng 3/5] whitespace and indentation Max Kellermann
2005-01-19 0:47 ` [PATCH pom-ng 4/5] use c99 initializers Max Kellermann
2005-01-19 0:47 ` [PATCH pom-ng 5/5] port the module to Linux 2.6 Max Kellermann
2005-01-19 8:30 ` [PATCH pom-ng 0/5] RFC: ip_nat|conntrack_h323.c on 2.6, first preview Jozsef Kadlecsik
2005-01-19 8:48 ` Max Kellermann
2005-01-19 8:56 ` Herve Eychenne
2005-01-19 9:06 ` Max Kellermann
2005-01-19 9:59 ` Jozsef Kadlecsik
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=20050119004611.GD12967@roonstrasse.net \
--to=max@duempel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=roberti@GoNetworks.com \
/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.