From: Patrick McHardy <kaber@trash.net>
To: Harald Welte <laforge@netfilter.org>
Cc: netfilter-devel@lists.netfilter.org,
Samir Bellabes <sbellabes@mandriva.com>
Subject: Re: [NETFILTER] Kill lockhelp.h for rtsp-conntrack
Date: Tue, 30 Aug 2005 23:49:58 +0200 [thread overview]
Message-ID: <4314D486.9040406@trash.net> (raw)
In-Reply-To: <20050830071102.GD4202@rama.de.gnumonks.org>
Harald Welte wrote:
> On Tue, Aug 30, 2005 at 01:00:42AM +0200, Patrick McHardy wrote:
>
>
>>>I mean that linux-2.6.11 don't need this patch at all.
>>>As far a you push 'kill lockhelp.h patch' in 2.6.13, people who use
>>>p-o-m with a kernel version < 2.6.13, should use lockhelp.h again.
>>>But now, this 3 patches will apply to all versions.
>>
>>I don't know what the general feeling about supporting old versions
>>in pom is, I would tend to ignore them if it means starting a third
>>linux subdirectory that should be maintained in some patchlets.
>>Harald, what is your opinion on this?
>
>
> I would rather start a new subdirectory than patching the old code.
> This way users of old kernels can have a working version, too (even if
> that old version doesn't have all the features or receives all the
> patches that newer versions do). At least as long as we're using the
> current patch-o-matic-ng, I think that's the way to go.
Ok, I'll fix it up tomorrow. Still something to discuss at the workshop
I think, putting time into maintaining compatibility with old kernels
is badly invested time IMO.
> When we decide do get rid of patch-o-matic-ng at some point, we
> obviously can also drop the 'old kernel' requirement.
Obviously :)
prev parent reply other threads:[~2005-08-30 21:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 17:27 [NETFILTER] Kill lockhelp.h for rtsp-conntrack Samir Bellabes
2005-08-29 17:33 ` Samir Bellabes
2005-08-29 20:53 ` Patrick McHardy
2005-08-29 22:36 ` Samir Bellabes
2005-08-29 23:00 ` Patrick McHardy
2005-08-30 7:11 ` Harald Welte
2005-08-30 21:49 ` Patrick McHardy [this message]
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=4314D486.9040406@trash.net \
--to=kaber@trash.net \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=sbellabes@mandriva.com \
/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.