All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Cc: Netfilter Mailinglist <netfilter@lists.netfilter.org>
Subject: Call for testing: patch-o-matic-ng
Date: Sun, 21 Dec 2003 13:24:45 +0100	[thread overview]
Message-ID: <20031221122445.GC5058@obroa-skai.de.gnumonks.org> (raw)

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

Hi!

I've now gotten patch-o-matic-ng to a state where it is actually quite
useable.  

Everybody interested can check it out from CVS
(netfilter/patch-o-matic-ng).  Everything should look exactly like the
old patch-o-matic, including screen output and command syntax.

However, the implementation behind the curtain is completely different.
Interested people are invited to look into the perl source of
Netfilter_POM.pm and 'runme'.

I would like to have people start testing/using pom-ng and report errors
back to me (via email).

The differences from a user's point of view:

- dependencies are resolved recursively
- verbose error reporting
- new, more verbose './runme --man' documentation
- if you want to apply a specific set of patches, don't prefix them
  with the repository name (i.e. use
  	./runme pptp-conntrack-nat
  instead of
  	./runme extra/pptp-conntrack-nat

The differences from a developer's point of view:

- support for requirements (i.e. kernel >= 2.4.22)
- recursive dependencies
- support for multiple kernel build systems (i.e. 2.4.x and 2.6.x)
- automatic creation of Configure.help entries / Kconfig help sections
  from the patches 'help' file
- no wholefile-patches in CVS.  This means that entirely new files like
  net/ipv4/netfilter/ipt_foo.c / ipt_foo.h are not stored as patches but
  rather in their original form.   This in turn means real version
  control on the sourcecode!
- backend seperated from frontend (i.e. other user frontends could be
  implemented
- not limited to the linux sourcecode.  It is easy to add support for
  other projects (if a patchlet would have to patch other software, too)

However, some stuff is still missing (see the patch-o-matic/TODO file).
I'm working on implementing those missing features, though.

-- 
- Harald Welte <laforge@netfilter.org>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

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

             reply	other threads:[~2003-12-21 12:24 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-21 12:24 Harald Welte [this message]
2003-12-22  9:56 ` Call for testing: patch-o-matic-ng KOVACS Krisztian
2003-12-22 12:00   ` Harald Welte
2003-12-23 14:57     ` Call for testing: patch-o-matic-ng (condition filter) Tim Gardner
2003-12-23 15:13       ` Call for testing: patch-o-matic-ng (fuzzy filter) Tim Gardner
2003-12-23 17:41       ` Call for testing: patch-o-matic-ng (condition filter) Harald Welte
2003-12-23 13:13 ` Call for testing: patch-o-matic-ng Gaël Le Mignot
2003-12-23 17:30   ` Harald Welte
2003-12-23 18:56     ` Unknown, Alistair Tonner
2003-12-24  0:26     ` Gaël Le Mignot
2003-12-24  1:03       ` Unknown, Alistair Tonner
2003-12-24  1:03         ` Unknown, Alistair Tonner
     [not found]     ` <200312231356.17135.Alistair Tonner <>
     [not found]       ` <200312231356.17135.AlistairTonner<>
2003-12-25  9:06         ` Galtar
2003-12-25  9:41           ` Antony Stone
2004-01-02 12:41 ` Henrik Nordstrom
2004-01-22 15:57 ` ip_conntrack_pptp Jan Kaastrup
2004-01-22 17:53   ` ip_conntrack_pptp Harald Welte
2004-01-22 18:09     ` ip_conntrack_pptp Unknown, Alistair Tonner
2004-01-22 18:09     ` ip_conntrack_pptp Unknown, Alistair Tonner
2004-01-22 18:09     ` ip_conntrack_pptp Unknown, Alistair Tonner
2004-01-22 19:41     ` ip_conntrack_pptp Arnt Karlsen
     [not found]     ` <000d01c3e3ed$9875b0f0$2d64a8c0@pcjka>
2004-01-26 16:19       ` ip_conntrack_pptp Harald Welte
2003-12-24  2:30 Call for testing: patch-o-matic-ng Vilmos Branyik
     [not found] <20031229154612.GB1417@obroa-skai.de.gnumonks.org>
     [not found] ` <Pine.LNX.4.33.0312310923090.9991-100000@blackhole.kfki.hu>
2004-01-01 16:36   ` Harald Welte
2004-01-05 11:32     ` Jozsef Kadlecsik
2004-01-05 11:55       ` Herve Eychenne
2004-01-05 12:03         ` Harald Welte
2004-01-05 12:45         ` Jozsef Kadlecsik
2004-01-05 13:22           ` Herve Eychenne
2004-01-06 10:32             ` Jozsef Kadlecsik
2004-01-06 13:37               ` Herve Eychenne
2004-01-05 15:28           ` Henrik Nordstrom

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=20031221122445.GC5058@obroa-skai.de.gnumonks.org \
    --to=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=netfilter@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.