From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 2/2] netfilter: Combine ipt_ttl and ip6t_hl source
Date: Wed, 18 Feb 2009 19:07:33 +0100 [thread overview]
Message-ID: <499C4E65.3050609@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0902181855570.8011@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Wednesday 2009-02-18 18:40, Patrick McHardy wrote:
>> Also applied, thanks. How about a compat config option for one
>> or two releases to keep the make oldconfig annoyance down?
>>
> This has been previously discussed with Sam or Roman, the end result
> being that kbuild does not quite support option fowarding - every
> symbol (e.g. OLD_TTL) that has no text will only be enabled if another
> symbol references it (thru 'select' for example) and otherwise any
> value, even one from .config, will be discarded and set to =n instead.
> But when OLD_TTL=n, the 'select NEW_TTL' on OLD_TTL will not take
> effect, and so on..
The alternative is to keep the text at the old options and have
them select a new hidden one. After two releases we move the
text over and kill the old ones.
But we really should do something about the constant kconfig
annoyance caused by these renames, let alone people who really
drop an option by accident and start bug hunting.
next prev parent reply other threads:[~2009-02-18 18:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 16:02 Combination patches, round 1 Jan Engelhardt
2009-02-18 16:02 ` [PATCH 1/2] netfilter: Combine ipt_TTL and ip6t_HL source Jan Engelhardt
2009-02-18 17:39 ` Patrick McHardy
2009-02-18 16:02 ` [PATCH 2/2] netfilter: Combine ipt_ttl and ip6t_hl source Jan Engelhardt
2009-02-18 17:40 ` Patrick McHardy
2009-02-18 17:59 ` Jan Engelhardt
2009-02-18 18:07 ` Patrick McHardy [this message]
2009-02-19 0:48 ` Jan Engelhardt
2009-02-19 10:16 ` 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=499C4E65.3050609@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).