Netdev List
 help / color / mirror / Atom feed
From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: dlstevens@us.ibm.com
Cc: davem@davemloft.net, netdev@oss.sgi.com, yoshfuji@linux-ipv6.org
Subject: Re: IPV6 RFC3542 compliance [PATCH]
Date: Tue, 07 Jun 2005 16:05:21 +0900 (JST)	[thread overview]
Message-ID: <20050607.160521.73986501.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <OF4AE6E385.33144EB9-ON88257019.0024BCE9-88257019.00258FFE@us.ibm.com>

In article <OF4AE6E385.33144EB9-ON88257019.0024BCE9-88257019.00258FFE@us.ibm.com> (at Mon, 6 Jun 2005 23:50:16 -0700), David Stevens <dlstevens@us.ibm.com> says:

> > Portable applications do like this:
> 
> > #ifdef IPV6_RECVHOPOPTS
> > // RFC2292bis
> > #else
> > // RFC2292
> > #endif
> 
> > --yoshfuji
> 
> I don't understand. If they do this, they'll
> work already when recompiled (with the patch
> I sent), won't they?

Yes (or they should do so before your favorite distro start shipping with
new constants).

> How does it help to renumber? I can renumber,
> of course-- I just don't see how that does
> anything.

We can still keep old binaries if we renumber.
This is important point.
e.g. people, including myself, can keep using old binaries on new kernels.

--yoshfuji

  reply	other threads:[~2005-06-07  7:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-06 19:48 IPV6 RFC3542 compliance [PATCH] David Stevens
2005-06-07  5:19 ` YOSHIFUJI Hideaki / 吉藤英明
2005-06-07  6:25   ` David Stevens
2005-06-07  6:33     ` YOSHIFUJI Hideaki / 吉藤英明
2005-06-07  6:50       ` David Stevens
2005-06-07  7:05         ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2005-06-07  7:40           ` David Stevens
2005-06-07  7:47             ` YOSHIFUJI Hideaki / 吉藤英明
2005-06-07  7:55               ` YOSHIFUJI Hideaki / 吉藤英明
2005-06-07  8:04                 ` David Stevens
2005-06-07  8:01               ` David Stevens
2005-06-07  8:14                 ` YOSHIFUJI Hideaki / 吉藤英明
2005-06-08 18:49                   ` David Stevens
2005-06-07  6:35     ` David Stevens

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=20050607.160521.73986501.yoshfuji@linux-ipv6.org \
    --to=yoshfuji@linux-ipv6.org \
    --cc=davem@davemloft.net \
    --cc=dlstevens@us.ibm.com \
    --cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox