From: Patrick McHardy <kaber@trash.net>
To: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: Update: Patch-o-matic cleanup
Date: Wed, 05 Apr 2006 17:37:46 +0200 [thread overview]
Message-ID: <4433E44A.3000503@trash.net> (raw)
In-Reply-To: <4433E035.2010504@gmx.net>
Carl-Daniel Hailfinger wrote:
> Hi Patrick,
>
> Patrick McHardy schrieb:
>
>>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[...]
>
>
> But why keep a few patches in pom and throw out the rest? Wouldn't it
> make sense to reduce pom to a simple script and throw out all patches?
> The few patches maintained by the netfilter team could be moved to a
> separate pom-hotfix package and be automatically downloaded by the
> pom script.
We could do that, but currently we want to keep a few patches while
minimizing our effort, the easiest way to do that is to just keep
them where they are.
> OTOH, having a pom-ng that can be applied without a network connection
> was very helpful for me in the past. So if you are really going to
> discontinue pom-ng as is, I offer to take over maintenance. Fetching
> the different packages from locations in a list and assembling them
> into one pom-full package automatically can't be that difficult.
I'm not sure if we want to discontinue official pom-releases entirely,
but you are of course free to maintain and release version which
include external patches.
next prev parent reply other threads:[~2006-04-05 15:37 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 ` Update: " Patrick McHardy
2006-04-05 15:20 ` Carl-Daniel Hailfinger
2006-04-05 15:37 ` Patrick McHardy [this message]
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=4433E44A.3000503@trash.net \
--to=kaber@trash.net \
--cc=c-d.hailfinger.devel.2006@gmx.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.