Date: Thu, 15 Nov 2012 11:22:47 -0500 From: Eitan Adler <eadler@freebsd.org> To: Alexey Dokuchaev <danfe@freebsd.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org, Ports Management Team <portmgr@freebsd.org> Subject: Re: svn commit: r307457 - head/Mk Message-ID: <CAF6rxg=TrZ3cdvRL8sOiyfr6uquNw%2BeC4xKv5F1fKNwo-w15sA@mail.gmail.com> In-Reply-To: <20121115161242.GA88933@FreeBSD.org> References: <201211151436.qAFEahgO099183@svn.freebsd.org> <CAF6rxgkh%2BWFoqo8ii8t6iOvu4zn_pHsAAVKZW%2BzDaaBZaFRXeg@mail.gmail.com> <20121115161242.GA88933@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15 November 2012 11:12, Alexey Dokuchaev <danfe@freebsd.org> wrote: > On Thu, Nov 15, 2012 at 10:08:06AM -0500, Eitan Adler wrote: >> On 15 November 2012 09:36, Alexey Dokuchaev <danfe@freebsd.org> wrote: >> > New Revision: 307457 >> > URL: http://svnweb.freebsd.org/changeset/ports/307457 >> > >> > Log: >> > Add SOCKS and STROKE options standard descriptions. >> >> Can portmgr please make it more clear what is and isn't permitted >> during a feature freeze? >> http://www.freebsd.org/portmgr/implementation.html would seem to say >> that this commit is not allowed (any commit to bsd.*.mk) but I've seen >> already a few commits to this file. > > Oops, technically you're right, sorry, didn't catch that *any* part. On > the other hand, I do not think this particular commit can break anything, > plus we already had branched. I can grep -R just to make sure. To be clear: I want portmgr to clarify this. I *don't* want this to be disallowed. The problem is that there isn't any document that is actually being followed that says "this is okay, but that isn't". -- Eitan Adler Source, Ports, Doc committer Bugmeister, Ports Security teams
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxg=TrZ3cdvRL8sOiyfr6uquNw%2BeC4xKv5F1fKNwo-w15sA>