From owner-cvs-ports@FreeBSD.ORG Tue Jul 13 19:48:56 2010 Return-Path: Delivered-To: cvs-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B54801065679 for ; Tue, 13 Jul 2010 19:48:56 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 5A3138FC27 for ; Tue, 13 Jul 2010 19:48:56 +0000 (UTC) Received: (qmail 1167 invoked by uid 399); 13 Jul 2010 19:48:54 -0000 Received: from localhost (HELO laptop.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 13 Jul 2010 19:48:54 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Date: Tue, 13 Jul 2010 12:48:52 -0700 (PDT) From: Doug Barton To: gahr@FreeBSD.org In-Reply-To: <20100713144735.GK48019@gahrfit.gahr.ch> Message-ID: References: <201007131351.o6DDpcmT044616@repoman.freebsd.org> <20100713144320.GA95556@FreeBSD.org> <20100713144735.GK48019@gahrfit.gahr.ch> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-message-flag: Outlook -- Not just for spreading viruses anymore! OpenPGP: id=1A1ABC84 Organization: http://SupersetSolutions.com/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: cvs-ports@FreeBSD.org, Alexey Dokuchaev , cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/devel/gdcm distinfo X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jul 2010 19:48:56 -0000 On Tue, 13 Jul 2010, Pietro Cerutti wrote: > Sure, "tarball rerolled" was meant to do just that :) The way this is usually done is to indicate in the commit message that you reviewed the diff between the old tarball and the new one, and a brief statement to describe what changed, and whether or not the change affected the installed version of the port. If the latter is true, a PORTREVISION bump is in order as well. This has nothing to do with whether or not we trust you to do your job. The commit logs serve (at least) 2 primary purposes. To let people know today what changed (briefly) and more importantly _why_ something changed. The other important purpose is to let people know what and why years from now, when no one remembers you. :) Another function that commit logs serve, and it's arguable whether or not it's a primary function, is to serve as an example to those who are reading them. We may all trust that YOU understand what "tarball rerolled" means, and why, but for someone new to the project who is going to be a committer someday, you want to set a good example. Based on what you said later in the thread a reasonable commit message might have been something like, "Tarball rerolled for a minor documentation update, no functional changes." hth, Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso