The future of patch-o-matic-ng

[Patrick McHardy]

Carl-Daniel Hailfinger wrote:
> Yes. I always treated pom-ng as patch collection which is usable
> offline. With the proposed change, it becomes a mix of patch
> collection and patch list. Packaging a patch list doesn't make
> sense, but packaging a link to a package list makes sense. If
> I already have to download patches on the machine where I want
> to apply them (no offline capability anymore), I can as well
> get the patch list from a link on the netfilter.org site.
> And if the linux machine has no network, I can simply download
> the packages via the link on the netfilter.org site on another
> machine.
> 
> Changing the name to pom-coreteam would give others the chance
> to provide a package with the same features and same name as
> the current pom-ng.

I honestly don't care about the name at all, but I don't really
see the point. We're pushing the good stuff to the kernel,
which should benefit everyone. Old, broken and obscure patches
are moved out, as are patches that are not ready for mainline
where we don't have enough interest in getting them ready ourselves.
You are of course welcome to work on these patches to get them
mergable. Ideally we will just obsolete pom.