All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anders Fugmann <afu@fugmann.dhs.org>
To: Harald Welte <laforge@gnumonks.org>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Fixed proken MARK target in POM.
Date: Fri, 10 Jan 2003 16:28:12 +0100	[thread overview]
Message-ID: <3E1EE68C.7030004@fugmann.dhs.org> (raw)
In-Reply-To: <20030110140024.GU1353@sunbeam.de.gnumonks.org>

Harald Welte wrote:
> On Thu, Jan 09, 2003 at 02:07:37PM +0100, Anders Fugmann wrote:
> 
> 
>>The patch maintains backward compability, and I request that this patch 
>>is applied to mainstream (and pushed to the Andrea for kernel 
>>inclusion), 
> 
> 
> 1) Where is the compatibility?  I cannot see how this code change would
>    ensure that
> 	a) old, unpatched kernel works with new, patched userspace
> 	b) new, patched kernel works with old, unpatched userspace
>    Those two conditions need to be fulfilled, otherwise we cannot make a
>    change during the stable kernel series.
I meant compability in form of userspace syntax, but I will make a new 
patch that sorts out the things above (if possible).

> 
> 2) Which Andrea are you talking about?  Therer is no Andrea involved in
>    netfilter/iptabls updates.
Andrea Arcangeli (2.4.x maintainer, just to recite what you already 
know), but as you wrote in the previous mail, all patches will go 
through netfilter-devel (And let the core team choose what to have 
included in the kernel).

> 
> 
>>as I as a software developer of a firewall cannot ask users 
>>of the software to appliy patches to POM.
> 
> 
> I regard this as critic to my recent patch-o-matic announcement, where I
> was asking people to use patch-o-matic.  I was talking about
Actually not, but thats ok.

> bugfixes/updates which are in 2.4.20 (or 2.4.21-preX)... but people are
> still running older kernels than that... and they should indeed use
> patch-o-matic for the netfilter fixes.
Agreed. Compability between kernel and userspace should be maintained no 
matter version, and patches exist in POM for users of older kernels.

> 
> Apart from that, everything in patch-o-matic are new features or
> extensions, which are either not fully stable or we strongly doubt that
> they are useful for the big public.  And if somebody wants to test one
> of those non-standard extensions, we can ask people to use patch-o-matic.
Yes. I'm aware of that. My question is "How can a patch be proven stable 
enough to be included, and is the functionality provided 'importent' 
enough for the general public?

Regards
Anders Fugmann

  reply	other threads:[~2003-01-10 15:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09 13:07 Fixed proken MARK target in POM Anders Fugmann
2003-01-10 14:00 ` Harald Welte
2003-01-10 15:28   ` Anders Fugmann [this message]
2003-01-10 16:38     ` Anders Fugmann
2003-01-11 19:16       ` Harald Welte
2003-01-12 19:58         ` Anders Fugmann
2003-01-11 19:23     ` Harald Welte

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=3E1EE68C.7030004@fugmann.dhs.org \
    --to=afu@fugmann.dhs.org \
    --cc=laforge@gnumonks.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.