All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: Scheduled removals
Date: Tue, 13 Jan 2009 05:44:51 +0100	[thread overview]
Message-ID: <496C1C43.3060401@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0901120703390.21692@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Monday 2009-01-12 05:32, Patrick McHardy wrote:
>>> as per Documentation/feature-removal-schedule.txt, some legacy code is ripe
>>> for removal. Now while pursuing this I wondered whether the struct definitions
>>> for the old code in the header files (e.g. in linux/netfilter/xt_CONNMARK.h)
>>> can also be removed or whether people will argue that doing so would
>>> unnecessarily cause dismay on behalf the potential users (of which there are
>>> not any). I am not aware of any users, and neither is Search Engine Google, so
>>> I'd just take the bait and kill it. Vetoes?
>> Every time I'm searching I do find some users of at least some
>> iptables headers. Maybe not this specific one, but that doesn't
>> mean much, fact is there might be users.
>>
>> That being said, I'd be fine removing both the functionality
>> and the headers after a sufficiently long period. I'm not
>> really confident that the period has indeed be long enough
>> though. When did we schedule this for removal?
> 
> January 2008.

OK, lets remove it in 2.6.30. At that point it should have been
almost 1.5 years, which seems to be enough.

      reply	other threads:[~2009-01-13  4:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06  3:32 Scheduled removals Jan Engelhardt
2009-01-12  4:32 ` Patrick McHardy
2009-01-12  6:03   ` Jan Engelhardt
2009-01-13  4:44     ` 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=496C1C43.3060401@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 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.