cvs commit: ports/graphics/osg Makefile ports/graphics/osg-devel Makefile ports/graphics/mapserver Makefile ports/math/saga Makefile ports/graphics/gdal Makefile distinfo pkg-plist ports/graphics/gdal/files gdalwarp.1 patch-ogr-GNUmakefile ...

Mark Linimon linimon at lonesome.com
Wed Aug 4 00:36:35 UTC 2010


I don't want to pick on osa in particular, as this is a problem I've
been tripping over in other commits the past week on a lot of ports:

On Tue, Aug 03, 2010 at 01:35:21PM +0000, Sergey A. Osokin wrote:
>   Modified files:
>     graphics/osg         Makefile 
>     graphics/osg-devel   Makefile 
>     graphics/mapserver   Makefile 
>     math/saga            Makefile 
>     graphics/gdal        Makefile distinfo pkg-plist 
>     graphics/gdal/files  patch-swig-python-GNUmakefile 
>   Removed files:
>     graphics/gdal/files  gdalwarp.1 patch-ogr-GNUmakefile 
>   Log:
>   Update from 1.6.0 to 1.7.2.

Although it's clear from the PR that it was graphics/gdal was the target
of the update, the problem that I've been finding is that commit messages
of the form "update from X to Y" are confusing when a) they don't defined
the port and b) dependent ports are committed at the same time.  This is
particularly true if one is looking through the cvs logs of a dependent
port, and trying to figure out exactly what was being changed.

Again, I'm not trying to pick on anyone in particular, this seems to
happen all over the place.  It just makes reading the cvs logs more of
a headache than they already are :-)

mcl


More information about the cvs-ports mailing list