Date: Tue, 19 Jan 2016 12:09:13 -0200 From: Raphael Kubo da Costa <rakuco@FreeBSD.org> To: Mathieu Arnold <mat@FreeBSD.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r406680 - in head: . net net/libproxy net/libproxy-gnome net/libproxy-gnome3 net/libproxy-kde net/libproxy-mozjs net/libproxy-perl net/libproxy-python net/libproxy-webkit net/libproxy/f... Message-ID: <86k2n5y83a.fsf@FreeBSD.org> In-Reply-To: <B87E2B5E3D55620D5158966D@atuin.in.mat.cc> (Mathieu Arnold's message of "Tue, 19 Jan 2016 12:02:48 %2B0100") References: <201601191000.u0JA0PtB036419@repo.freebsd.org> <B87E2B5E3D55620D5158966D@atuin.in.mat.cc>
next in thread | previous in thread | raw e-mail | index | archive | help
Mathieu Arnold <mat@FreeBSD.org> writes: > +--On 19 janvier 2016 10:00:25 +0000 Raphael Kubo da Costa > <rakuco@FreeBSD.org> wrote: > | Added: > | head/net/libproxy-gnome3/ > | head/net/libproxy-gnome3/Makefile (contents, props changed) > | head/net/libproxy-gnome3/pkg-descr (contents, props changed) > | head/net/libproxy-gnome3/pkg-plist (contents, props changed) > > This should have been copied from the libproxy-gnome port, not added as a > new one. I considered doing that, but then decided in favor of not using svn cp just because even though the ports are similar this is just by chance (I wouldn't use svn cp to add, say, libproxy-natus or libproxy-dotnet).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86k2n5y83a.fsf>