Date: Mon, 1 Mar 2004 09:00:38 -0500 (EST) From: Robert Watson <rwatson@FreeBSD.org> To: "Andrey A. Chernov" <ache@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/locale setlocale.c Message-ID: <Pine.NEB.3.96L.1040301085614.62987F-100000@fledge.watson.org> In-Reply-To: <200403011143.i21Bhoap028383@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 1 Mar 2004, Andrey A. Chernov wrote: > ache 2004/03/01 03:43:50 PST > > FreeBSD src repository > > Modified files: (Branch: RELENG_5_2) > lib/libc/locale setlocale.c > Log: > MFC important bugfixes from v1.49-1.50 > > Revision Changes Path > 1.48.2.1 +39 -26 src/lib/libc/locale/setlocale.c I don't see an "Approved by:" here, nor any sign of this change being run by security-officer or the release engineering team. The release engineering page clearly identifies this branch as frozen, requiring release engineering approval: http://www.FreeBSD.org/releng/ Could you tell me who approved this commit? The release engineering branches are under very careful control because they are used to generate binary updates, etc, especially immediately following a release, and unapproved commits are not acceptable, especially given clear documentation of the purpose of the branch, as well as the process for committing to it. This isn't just a matter of "is the commit content sufficient to merit inclusion", but also an issue as to the point in the release engineering process, adequate evaluation and testing, and its impact on the release notes, errata, et al. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1040301085614.62987F-100000>