Date: Mon, 27 Jul 2015 19:34:44 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Bryan Drewery <bdrewery@FreeBSD.org> Cc: Mathieu Arnold <mat@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r392818 - head/Mk/Scripts Message-ID: <20150727193444.GA33027@FreeBSD.org> In-Reply-To: <55B661EA.3000003@FreeBSD.org> References: <201507241105.t6OB5sfH046007@repo.freebsd.org> <55B2722C.40406@FreeBSD.org> <20150725130348.GA17582@FreeBSD.org> <55B661EA.3000003@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jul 27, 2015 at 09:52:58AM -0700, Bryan Drewery wrote: > On 7/25/15 6:03 AM, Alexey Dokuchaev wrote: > > On Fri, Jul 24, 2015 at 10:13:16AM -0700, Bryan Drewery wrote: > >> On 7/24/15 4:05 AM, Mathieu Arnold wrote: > >>> New Revision: 392818 > >>> URL: https://svnweb.freebsd.org/changeset/ports/392818 > >>> > >>> Log: > >>> [Forced commit to explain the previous commit] > >> > >> God I wish these were blocked. > > > > I'm not sure I catch it, what's wrong with forced commits? (Modulo the > > fact that they have to be made in a hackish way with SVN.) > > The only benefit is for mails and 'svn log file'. It does not properly > fix the log for 'svn blame' which is what I primarily use when I am > looking at code; I never see these forced commit messages. Hm, it didn't occur to me what forced commits do not leave a trace with "svn blame"; thanks for the insight Bryan! ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150727193444.GA33027>