Date: Wed, 10 Oct 2001 16:22:24 +0100 From: Brian Somers <brian@freebsd-services.com> To: Maxim Sobolev <sobomax@FreeBSD.org> Cc: Paul Richards <paul@freebsd-services.com>, Garance A Drosihn <drosih@rpi.edu>, Brian Somers <brian@freebsd-services.com>, Mike Barcroft <mike@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, brian@freebsd-services.com Subject: Re: cvs commit: src/lib/libc/string strnstr.c Makefile.inc strstr.3src/include string.h Message-ID: <200110101522.f9AFMOg11391@hak.lan.Awfulhak.org> In-Reply-To: Message from Maxim Sobolev <sobomax@FreeBSD.org> of "Wed, 10 Oct 2001 18:13:17 %2B0300." <3BC4658D.2D91B7D8@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Paul Richards wrote:
>
> > --On Tuesday, October 09, 2001 11:12:25 -0400 Garance A Drosihn
> > <drosih@rpi.edu> wrote:
> >
> > > At 10:55 AM +0100 10/9/01, Brian Somers wrote:
> > >> > mike 2001/10/08 18:29:56 PDT
> > >> > Log:
> > >>> Add a new libc function, strnstr(3), which allows one to limit the
> > >>> number of characters that are searched. This is especially useful
> > >>> with file operations and non-NUL terminated strings.
> > >>>
> > >>> Silence from: -audit, -hackers
> > >> > MFC after: 5 days
> > >>
> > >> Is this based on any known standard ? If not, shouldn't there be
> > >> a mention that this is a FreeBSD specific API in the man page ?
> > >
> > > That sounds like a good idea to me.
> > >
> > >> Also, does this need to be MFC'd (I would say not), and does
> > >> __FreeBSD_version need to be bumped ?
> > >
> > > Why wouldn't we MFC this? As I understand it, this routine has been
> > > added to fix a problem. Why wouldn't we want to make that fix
> > > available for -stable? Why wait a year (for 5.0 to become the
> > > stable branch)?
> >
> > It only fixes a problem if you rewrite the applications to use it, and then
> > those applications won't run on earlier 4.x branches.
> >
> > I'm not sure the rule of not breaking binary compatibility across -stable
> > branches has any relevance any more though since it's already a screwed
> > policy.
>
> Correct me if I am wrong, but we never actually were strongly enforcing forward
> binary compatibility, so that it should not be a big problem.
I've always understood the rule to be that -stable remains binary
compatible (both forwards and backwards) while the major release
number is the same.
> -Maxim
--
Brian <brian@freebsd-services.com> <brian@Awfulhak.org>
http://www.freebsd-services.com/ <brian@[uk.]FreeBSD.org>
Don't _EVER_ lose your sense of humour ! <brian@[uk.]OpenBSD.org>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110101522.f9AFMOg11391>