All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Update: Patch-o-matic cleanup
Date: Wed, 05 Apr 2006 15:47:33 +0200	[thread overview]
Message-ID: <4433CA75.9040607@trash.net> (raw)
In-Reply-To: <443165AA.4030509@trash.net>

Patrick McHardy wrote:
> Following (quite late) the decision taken at the netfilter workshop to
> clean up the pomng repository by removing old patches and moving some
> patches out of the netfilter repository, I've started by removing the
> obsolete ipsec* patches and the policy match. Both have been merged
> and were pretty outdated.
> 
> If noone can name good reasons against it, I will also remove the
> following patches in a few days:
> [...]

After receiving multiple "please keep this patch" mails, it seems I
started the wrong way.

Removing old patches is part of a greater plan to reduce the content of
pom to only those things the netfilter team has an interest in
maintaining, and most of these things will be merged in not too long
time. _All_ other patches will be removed and the "runme" tool will
be enhanced by an apt-get like mechanism to download patches from
external sources, so people interested in keeping patches around can
maintain them themselves and publish them somewhere for others to use.
This should benefit both us and the authors since they usually maintain
their own versions of the patches anyway and periodically send us
updates to include in pom, which unnecessarily cost time for everyone
involved.

This is the full list of patches to be removed. Instructions how to set
up a pomng repository are at the end of this mail, I'll commit the code
soon.

- ACCOUNT
- IPMARK
- NETLINK
- NETMAP
- TARPIT
- TCPLAG
- TRACE
- XOR
- account
- comment
- connlimit
- connrate
- conntrack_locking
- cuseeme-nat
- dropped-table
- expire
- fuzzy
- geoip
- goto
- ip_queue_vwmark
- ipp2p
- mport
- nat-reservations
- netfilter-docbook
- osf
- owner-socketlookup
- pool
- pptp-conntrack-nat
- psd
- time
- tproxy

The patches will be removed in 30 days, authors or other people that
want to maintain them in an external repository are welcome to send
the URL to be included in the distrubuted sources.list.

How to set up a repository:

The repository must be accessible in a way supported by curl (HTTP or
FTP for example). The name of each patchlet is listed in a file named
"index". Each patchlet must be contained in a .tar.gz file, which
contains a directory named like the patchlet itself. The directories
contents are similar to those in patchlets/ today, but the Repository
specified in the info file must be "external".

So to create a repository from one of the patches currently in pom:

- cd patchlets
- edit $patch/info, change repository to "external"
- tar cz $patch > /wwwroot/pom-repo/$patch.tar.gz
- echo $patch >> /wwwroot/pom-repo/index

As I said above, I'll commit the code for this soon.

  parent reply	other threads:[~2006-04-05 13:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-03 18:12 Patch-o-matic cleanup Patrick McHardy
2006-04-04  6:26 ` Stephen Jones
2006-04-04  8:38   ` Patrick McHardy
2006-04-04 14:39     ` Stephen Jones
2006-04-04  8:04 ` Krzysztof Oledzki
2006-04-04  8:54 ` Samuel Díaz García
2006-04-05 13:27   ` Patrick McHardy
2006-04-04  9:19 ` Carl-Daniel Hailfinger
2006-04-04 19:57 ` Samuel Díaz García
2006-04-05 13:47 ` Patrick McHardy [this message]
2006-04-05 15:20   ` Update: " Carl-Daniel Hailfinger
2006-04-05 15:37     ` Patrick McHardy
2006-04-05 15:29   ` Harald Welte
2006-04-30 10:44   ` Thomas Jarosch
2006-05-02 14:01     ` Patrick McHardy
2006-05-12  5:55   ` Patrick McHardy
2006-05-12 10:17     ` Carl-Daniel Hailfinger
2006-05-12 10:26       ` 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=4433CA75.9040607@trash.net \
    --to=kaber@trash.net \
    --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.