All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: Patrick Schaaf <bof@bof.de>
Cc: Harald Welte <laforge@netfilter.org>,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>,
	Patrick McHardy <kaber@trash.net>,
	Grzegorz Janoszka <Grzegorz@Janoszka.pl>
Subject: Re: The future of patch-o-matic-ng
Date: Thu, 06 Apr 2006 15:42:13 +0200	[thread overview]
Message-ID: <44351AB5.9090103@gmx.net> (raw)
In-Reply-To: <20060406131939.GA19216@oknodo.bof.de>

Patrick Schaaf schrieb:
>>So if you really don't want to package patches from other sources
>>anymore, please be honest and call the new package pom-coreteam
>>or something like that.
> 
> What has honesty to do with naming things?

Sorry, english is my second language. Maybe "broken expectation"
would be a better description.

> As far as I can see, the core team is honestly telling us what
> they are going to do, and why. Happy naming games don't enter
> into this feeling of mine.

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.

Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/

  reply	other threads:[~2006-04-06 13:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-03 22:09 Trivial connlimit and IPMARK patch for 2.6.16 Grzegorz Janoszka
2006-04-05 15:26 ` Harald Welte
     [not found]   ` <Pine.GSO.4.63.0604052144350.1472@galaxy.agh.edu.pl>
2006-04-06  7:35     ` The future of patch-o-matic-ng Harald Welte
2006-04-06  8:22       ` Patrick McHardy
2006-04-06 10:34         ` Krzysztof Oledzki
2006-04-06 10:40           ` Patrick McHardy
2006-04-06 11:42             ` Krzysztof Oledzki
2006-04-06 10:53           ` Harald Welte
2006-04-06 13:14             ` Carl-Daniel Hailfinger
2006-04-06 13:19               ` Patrick Schaaf
2006-04-06 13:42                 ` Carl-Daniel Hailfinger [this message]
2006-04-06 14:30                   ` Patrick McHardy
2006-04-06 14:23               ` Patrick McHardy
     [not found]       ` <Pine.GSO.4.63.0604061447420.22707@galaxy.agh.edu.pl>
2006-04-06 14:31         ` 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=44351AB5.9090103@gmx.net \
    --to=c-d.hailfinger.devel.2006@gmx.net \
    --cc=Grzegorz@Janoszka.pl \
    --cc=bof@bof.de \
    --cc=kaber@trash.net \
    --cc=laforge@netfilter.org \
    --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.