All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] Reserve nfnetlink subsys ids.
Date: Fri, 12 Jun 2009 14:08:56 +0200	[thread overview]
Message-ID: <4A324558.3020506@trash.net> (raw)
In-Reply-To: <alpine.DEB.2.00.0906112349380.30129@blackhole.kfki.hu>

Jozsef Kadlecsik wrote:
> On Thu, 11 Jun 2009, Patrick McHardy wrote:
> 
>> Pablo Neira Ayuso wrote:
>>> Patrick McHardy wrote:
>>>> Jozsef Kadlecsik wrote:
>>>>> Hi Patrick,
>>>>>
>>>>> A tiny patch to add nfnetlink subsys ids for nftables and ipset. :-)
>> As I said, IDs are usually not reserved until something is merged,
>> even if there is agreement to merge it. I guess there has been too
>> much bad experience with reserved IDs and code that never got merged.
>> I have to justify the patches I merge myself and so far I can't.
> 
> You're right, of course. I'm going to find another way for a smooth 
> protocol migration.

I didn't mean to finally say no, just wondering if there are special
circumstances which would justify an exception.

  reply	other threads:[~2009-06-12 12:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11 11:36 [PATCH] Reserve nfnetlink subsys ids Jozsef Kadlecsik
2009-06-11 14:08 ` Patrick McHardy
2009-06-11 14:26   ` Pablo Neira Ayuso
2009-06-11 14:43     ` Pablo Neira Ayuso
2009-06-11 14:49     ` Patrick McHardy
2009-06-11 21:51       ` Jozsef Kadlecsik
2009-06-12 12:08         ` Patrick McHardy [this message]
2009-06-12 13:02           ` Jozsef Kadlecsik
2009-06-12 13:07             ` Patrick McHardy
2009-06-12 13:18               ` Jan Engelhardt

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=4A324558.3020506@trash.net \
    --to=kaber@trash.net \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@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.