Date: Sat, 25 Jan 2014 23:29:09 +0400 From: Ruslan Makhmatkhanov <cvs-src@yandex.ru> To: Matthew Seaman <matthew@FreeBSD.org>, Mathieu Arnold <mat@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-svnadmin@freebsd.org Subject: Re: svn commit: r341044 - in svnadmin/hooks: . scripts Message-ID: <52E41085.1010405@yandex.ru> In-Reply-To: <52E40C96.6000406@FreeBSD.org> References: <201401251537.s0PFbGgR069885@svn.freebsd.org> <52E40937.9060002@yandex.ru> <52E40C96.6000406@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Seaman wrote on 25.01.2014 23:12: > On 25/01/2014 18:57, Ruslan Makhmatkhanov wrote: >> Mathieu Arnold wrote on 25.01.2014 19:37: >>> Author: mat >>> Date: Sat Jan 25 15:37:15 2014 >>> New Revision: 341044 >>> URL: http://svnweb.freebsd.org/changeset/ports/341044 >>> QAT: https://qat.redports.org/buildarchive/r341044/ >>> >>> Log: >>> Add a hook to forbid committing to vulk.xml and other files at the >>> same time. >> >> I may miss some discussion about this, but what the point of this >> change? Last time I ever hear about vuln.xml practice it was recommended >> to group related changes into a single commit. For example, update the >> port to version where vulnerability was fixed with associated vuln.xml >> entry. >> > > vuln.xml changes need to be merged to 2014Q1 and similar branches, but > associated changes to vulnerable ports may need different fixes in > different branches. > > Cheers, > > Matthew > That makes sense. Thank you. -- Regards, Ruslan T.O.S. Of Reality
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52E41085.1010405>