Date: Sat, 05 Nov 2011 12:56:35 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Alexey Dokuchaev <danfe@FreeBSD.org> Cc: cvs-ports@FreeBSD.org, Philippe Aud?oud <jadawin@FreeBSD.org>, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/graphics/darktable Makefile Message-ID: <4EB594F3.5060301@FreeBSD.org> In-Reply-To: <20111104094842.GB96244@FreeBSD.org> References: <201111040923.pA49NfeX002682@repoman.freebsd.org> <20111104093039.GA89435@tuxaco.net> <20111104094842.GB96244@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/04/2011 02:48, Alexey Dokuchaev wrote: > On Fri, Nov 04, 2011 at 10:30:39AM +0100, Philippe Aud?oud wrote: >> On Fri, 04 Nov 2011, Alexey Dokuchaev wrote: >>> danfe 2011-11-04 09:23:41 UTC >>> >>> Modified files: >>> graphics/darktable Makefile >>> Log: >>> Allow to build without rawspeed backend (use libraw instead). >>> >>> Revision Changes Path >>> 1.20 +8 -0 ports/graphics/darktable/Makefile >> >> Why two commit for two changes in one port? > > One port, but two totally unrelated commits to two unrelated (separate) > files. Imagine doing "cvs log" on pkg-descr: why pollute the results with > something which obviously had nothing to do with it? > > Ditto for Makefile. +1 Keeping the cvs logs relevant to the files that they are attached to is a feature. :) -- "We could put the whole Internet into a book." "Too practical." Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EB594F3.5060301>