From owner-cvs-all Wed Oct 10 7:44:57 2001 Delivered-To: cvs-all@freebsd.org Received: from mailgate.originative.co.uk (mailgate.originative.co.uk [62.232.68.68]) by hub.freebsd.org (Postfix) with ESMTP id 8B6DF37B405; Wed, 10 Oct 2001 07:44:42 -0700 (PDT) Received: from lobster.originative.co.uk (lobster [62.232.68.81]) by mailgate.originative.co.uk (Postfix) with ESMTP id 3ED7E1D169; Wed, 10 Oct 2001 15:44:40 +0100 (BST) Date: Wed, 10 Oct 2001 15:44:40 +0100 From: Paul Richards To: Garance A Drosihn , Brian Somers , Mike Barcroft Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/string strnstr.c Makefile.inc strstr.3 src/include string.h Message-ID: <1468350000.1002725080@lobster.originative.co.uk> In-Reply-To: References: <200110090955.f999tT490240@hak.lan.Awfulhak.org> X-Mailer: Mulberry/2.1.0 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --On Tuesday, October 09, 2001 11:12:25 -0400 Garance A Drosihn 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. Paul Richards FreeBSD Services Ltd http://www.freebsd-services.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message