Date: Mon, 27 Aug 2007 20:10:02 +0400 From: Yar Tikhiy <yar@comp.chem.msu.su> To: John Baldwin <jhb@freebsd.org> Cc: src-committers@freebsd.org, Peter Jeremy <peterjeremy@optushome.com.au>, Alfred Perlstein <alfred@freebsd.org>, cvs-all@freebsd.org, Daniel Eischen <deischen@freebsd.org>, cvs-src@freebsd.org Subject: Re: cvs commit: src/lib/libc/gen fts-compat.c fts-compat.h Message-ID: <20070827161002.GO21352@comp.chem.msu.su> In-Reply-To: <200708270939.48788.jhb@freebsd.org> References: <200708230509.l7N59VCi048341@repoman.freebsd.org> <Pine.GSO.4.64.0708241819220.13181@sea.ntplx.net> <20070825050637.GF99474@comp.chem.msu.su> <200708270939.48788.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 27, 2007 at 09:39:47AM -0400, John Baldwin wrote: > On Saturday 25 August 2007 01:06:37 am Yar Tikhiy wrote: > > On Fri, Aug 24, 2007 at 06:25:17PM -0400, Daniel Eischen wrote: > > > I never added symbol versioning to libc in order to solve > > > -current upgrade problems. Sure, you're free to use it that > > > way, but it would not make me very happy ;-) > > > > You put it as though symbol versioning is your area of interest and > > you just don't want any intruders to tamper with it. It wouldn't > > have seemed so if there had been a well-defined policy on symbol > > versioning usage somewhere on www.freebsd.org. > > No, there isn't a well-defined policy currently, feel free to write it > down. :) I think I'll write it down when this issue has been settled and I have enough input data. I like writing docs as I have rather poor long-term memory and often consult my own texts. :-) -- Yar
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070827161002.GO21352>