Date: Mon, 26 Jan 2004 13:53:22 -0600 From: "Jacques A. Vidrine" <nectar@FreeBSD.org> To: Garance A Drosihn <drosih@rpi.edu> Cc: src-committers@FreeBSD.org Subject: Re: cvs commit: src/contrib/cvs/src server.c Message-ID: <20040126195322.GA76044@madman.celabo.org> In-Reply-To: <p06020496bc3b163cb851@[128.113.24.47]> References: <200401260008.i0Q08cIl014780@repoman.freebsd.org> <20040126000922.GA6102@madman.celabo.org> <20040126004123.GJ53344@elvis.mu.org> <20040126125638.GC9772@madman.celabo.org> <p06020496bc3b163cb851@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 26, 2004 at 02:13:44PM -0500, Garance A Drosihn wrote: > I have no objection to the change, but it does seem to me that > *any* change to a "security" branch deserves to be mentioned > in UPDATING. I do not agree that we should ignore that policy > simply because this is a "5.x-release" branch. RELENG_5_2 is not really a security branch yet, as it is still in the release engineer's hands. If this CVS change needs an UPDATING entry, then every merge we've done needs an UPDATING entry. I'll leave that up to RE. (RE has already documented the changes in the release notes.) Cheers, -- Jacques Vidrine NTT/Verio SME FreeBSD UNIX Heimdal nectar@celabo.org jvidrine@verio.net nectar@freebsd.org nectar@kth.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040126195322.GA76044>