All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira <pablo@eurodev.net>
To: Sven Anders <anders@anduras.de>
Cc: netfilter-devel@lists.netfilter.org,
	Bart De Schuymer <bdschuym@pandora.be>
Subject: Re: New iptables structure
Date: Sun, 28 Nov 2004 21:45:49 +0100	[thread overview]
Message-ID: <41AA38FD.5050805@eurodev.net> (raw)
In-Reply-To: <41A85AC4.5080006@anduras.de>

Sven Anders wrote:

> Why not break compatibilty, if it hamper the development?


I don't see things that way, compatibility could be broken if all 
developers get their brains broken or become insane because they aren't 
able to workaround a problem. That didn't happen at the moment :)

> To prevent further incompatibility, you can insert some reserved 
> fields to the main
> structure...


it's not that easy, you can't always guess where they will come from. So 
we can't reserve a field in every structure.

I agree with Bart, backward compatibility is important.

--
Pablo

  parent reply	other threads:[~2004-11-28 20:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-25  4:49 [PATCH 1/2] ipt_MARK extension with backwards compatibility (kernel side) Rusty Russell
2004-11-26 22:58 ` Pablo Neira
2004-11-27 10:45   ` New iptables structure (was: [PATCH 1/2] ipt_MARK extension with backwards compatibilty...) Sven Anders
2004-11-27 14:14     ` Bart De Schuymer
2004-11-28 20:45     ` Pablo Neira [this message]
2004-11-29 12:27     ` Henrik Nordstrom
2004-12-07 21:20   ` [PATCH 1/2] ipt_MARK extension with backwards compatibility (kernel side) Pablo Neira
2004-12-08  5:44     ` Rusty Russell

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=41AA38FD.5050805@eurodev.net \
    --to=pablo@eurodev.net \
    --cc=anders@anduras.de \
    --cc=bdschuym@pandora.be \
    --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.