From owner-svn-ports-all@FreeBSD.ORG Sat Jan 25 19:29:24 2014 Return-Path: Delivered-To: svn-ports-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9953626D; Sat, 25 Jan 2014 19:29:24 +0000 (UTC) Received: from forward1l.mail.yandex.net (forward1l.mail.yandex.net [IPv6:2a02:6b8:0:1819::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4C8051B7B; Sat, 25 Jan 2014 19:29:24 +0000 (UTC) Received: from smtp11.mail.yandex.net (smtp11.mail.yandex.net [95.108.130.67]) by forward1l.mail.yandex.net (Yandex) with ESMTP id B72181520DB2; Sat, 25 Jan 2014 23:29:20 +0400 (MSK) Received: from smtp11.mail.yandex.net (localhost [127.0.0.1]) by smtp11.mail.yandex.net (Yandex) with ESMTP id 22DAF7E0098; Sat, 25 Jan 2014 23:29:20 +0400 (MSK) Received: from unknown (unknown [178.76.234.16]) by smtp11.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id HEahOEe7vG-TJWWECbW; Sat, 25 Jan 2014 23:29:19 +0400 (using TLSv1 with cipher CAMELLIA256-SHA (256/256 bits)) (Client certificate not present) X-Yandex-Uniq: a9b4ddc1-7afe-405f-8a98-fc54c75222eb DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1390678159; bh=UmyvZIFYi1eSzek5QWF3Ut/SLfb0Botb23FBWz1ISwk=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Gn10EXJ7H1UX5L2XKTbntuKedX9/hkF0lvwCkbLt1K3r7MOOfWZVQ0brwXRwp6LQi yaxovOV6e6QJvktPL48WlkoBD5T0RTumBTfWqVL9KLNf1up8d74bhKsh2JKon3U6h9 CVZmLBdzLgcWvUOvd/eK0X+502OJk0bmPmnnq6jM= Authentication-Results: smtp11.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <52E41085.1010405@yandex.ru> Date: Sat, 25 Jan 2014 23:29:09 +0400 From: Ruslan Makhmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Matthew Seaman , Mathieu Arnold , ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-svnadmin@freebsd.org Subject: Re: svn commit: r341044 - in svnadmin/hooks: . scripts References: <201401251537.s0PFbGgR069885@svn.freebsd.org> <52E40937.9060002@yandex.ru> <52E40C96.6000406@FreeBSD.org> In-Reply-To: <52E40C96.6000406@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 19:29:24 -0000 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