From owner-svn-ports-all@freebsd.org Wed Jul 18 07:59:54 2018 Return-Path: Delivered-To: svn-ports-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA982103D58C; Wed, 18 Jul 2018 07:59:54 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 56E4C8DDE1; Wed, 18 Jul 2018 07:59:54 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by fc.opsec.eu with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1ffhNG-0006Cw-UT; Wed, 18 Jul 2018 09:59:50 +0200 Date: Wed, 18 Jul 2018 09:59:50 +0200 From: Kurt Jaeger To: Mathieu Arnold Cc: Yuri , ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r474820 - in head/graphics: . diff-pdf Message-ID: <20180718075950.GY967@fc.opsec.eu> References: <201807171752.w6HHqPGY086343@repo.freebsd.org> <20180717205936.vknaxlrewnjv5rsc@atuin.in.mat.cc> <98365d7c-b252-f0b6-77ee-fe7e37474e33@freebsd.org> <20180718072531.kauobgwo5xidvv5j@atuin.in.mat.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180718072531.kauobgwo5xidvv5j@atuin.in.mat.cc> X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.27 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: Wed, 18 Jul 2018 07:59:55 -0000 Hi! > On Tue, Jul 17, 2018 at 05:28:03PM -0700, Yuri wrote: > > On 07/17/18 13:59, Mathieu Arnold wrote: > > > The PR adds version 0.2. Any good reason why you silently updated the > > > software without asking the maintainer about it? > > > > > > Yes, there is a good reason: the version 0.2 is from May 23, 2013, and the > > latest commit is much more recent, only 7 months old. > > That is a reason, a bad one maybe. Certainly not a good one. Why did > not you consult with the maintainer before updating the port he created? > How can you be sure he aggres with it? That is a *bit* over the top. No sane maintainer will complain if the committer updates the submitted port to a newer version, as long as functionality isn't affected. -- pi@FreeBSD.org +49 171 3101372 2 years to go !