From: Chip Salzenberg <chip@pobox.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Steve Dickson <SteveD@redhat.com>,
nfs@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: nfs-utils-1.0.5 is not backwards compatible with 2.4
Date: Fri, 1 Aug 2003 10:38:07 -0400 [thread overview]
Message-ID: <20030801143807.GB24358@perlsupport.com> (raw)
In-Reply-To: <16169.54918.472349.928145@gargle.gargle.HOWL>
According to Neil Brown:
> I don't know if there is any such code, but if there is I apoligize for
> breaking it and suggest that the best fix is to not use the header
> file it was using but it explicitly include the values for NFSEXP_* in
> that code.
The only really bad thing about the current situation is that the name
"NFSEXP_CROSSMNT" is poisoned by having had two historical
definitions. So it that name should be dropped, IMO, and replaced by
something textually different. "NFSEXP_XMOUNT", perhaps. Even
"NFSEXP_CROSSMNT2" would work. Just as long as code that said
"CROSSMNT" to mean "NOHIDE" wouldn't accidentally get CROSSMNT instead.
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K
next prev parent reply other threads:[~2003-08-01 14:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 17:12 nfs-utils-1.0.5 is not backwards compatible with 2.4 Steve Dickson
2003-07-31 18:23 ` Kernel 2.4 and 2.6 disagree about NFSEXP_CROSSMNT - upward incompatibility, please fix Chip Salzenberg
2003-07-31 22:05 ` Andrew Morton
2003-08-01 2:55 ` nfs-utils-1.0.5 is not backwards compatible with 2.4 Neil Brown
2003-08-01 12:43 ` Steve Dickson
2003-08-04 0:52 ` Neil Brown
2003-08-04 0:52 ` Neil Brown
2003-08-01 14:38 ` Chip Salzenberg [this message]
2003-08-04 0:55 ` Neil Brown
2003-08-04 0:55 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2003-07-31 16:05 Steve Dickson
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=20030801143807.GB24358@perlsupport.com \
--to=chip@pobox.com \
--cc=SteveD@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
/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.