Date: Sat, 4 Jun 2005 14:22:20 +0200 From: Erwin Lansing <erwin@lansing.dk> To: Sam Lawrance <lawrance@FreeBSD.org> Cc: cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/databases/clip/files patch-cliplibs_clip-gtk2_Makefile.in Message-ID: <20050604122220.GH70125@droso.net> In-Reply-To: <1117887511.758.33.camel@dirk.no.domain> References: <200506040254.j542sFcL007764@repoman.freebsd.org> <20050604114406.GF70125@droso.net> <1117887511.758.33.camel@dirk.no.domain>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Sat, Jun 04, 2005 at 10:18:31PM +1000, Sam Lawrance wrote: > On Sat, 2005-06-04 at 13:44 +0200, Erwin Lansing wrote: > > On Sat, Jun 04, 2005 at 02:54:15AM +0000, Sam Lawrance wrote: > > > lawrance 2005-06-04 02:54:15 UTC > > > > > > FreeBSD ports repository > > > > > > Added files: > > > databases/clip/files patch-cliplibs_clip-gtk2_Makefile.in > > > Log: > > > Add a patch missed on the last update. > > > > How can there be a previous update for a new file? > > > > It can happen when a file is added, updated, then removed, then re-added > again. > > Although, I don't think that's what you're really asking ;-) The log No, it wasn't :) > could have been clearer. What I meant was "add a patch missed on the > last update to the port". > What I ment to say was that you should have included the commit message from the last update as well. Otherwise it will be impossible to know what the *functional* change was when someone is browsing cvs-logs in a year time. Cheers, -erwin "cvs police" lansing -- Erwin Lansing DISCLAIMER: No electrons were harmed while sending this message. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCoZz8qy9aWxUlaZARAuOpAKCCZ1GsrIu0qDM1y07D5/IbchwCCACg9fcN Deb2RaWFnM+Ch0Wr4ygu+Xk= =Aqyg -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050604122220.GH70125>