Bernhard Reiter bernhard at intevation.de
Thu Aug 23 12:13:19 EDT 2001

Some information might be lost by CVS commands.
Source is never lost, but tags might.

In removing the irritating tag, which never should have been created
in the first place, I also eliminated information on which files
were on the tags.

Check the cvs status output which describes per file which revisions
are tagged for what. cvs log describes which changes were done between 

All in all reading the Cederquist and examining the outputs of these
commands will deeped your cvs knowledge for the future I think.
So it is worth the time. 

Sorry that I cannot answer all questions in complete detail.

On Thu, Aug 23, 2001 at 05:24:54PM +0200, Markus Neteler wrote:
> another followup:
> I still try to understand *how* to interplete the cvs log file. As I
> remember Glynn had the problem that d.rgb was added to the wrong
> (non-)branch or whatever. So I focus on this module to understand
> what's going on here.
> So, using:
> cvs log -d">2001-05-20" -r:releasebranch_11_april_2001_5_0_0 -wglynn |grep -v OBJ
> to check for "glynn"'s checkins I have seen that d.rgb lives in the
> "Attic" of CVS (most of other modules not).
> Might the "Attic"-home of a module be an indicator for something has been
> gone wrong?
> Well, unless someone knows how use the "cvs log" in a useful manner,
> I'll stop the investigation...
> Markus
> _______________________________________________
> grass5 mailing list
> grass5 at grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass5

Professional Service around Free Software                (intevation.net)  
The FreeGIS Project                                         (freegis.org)
Association for a Free Informational Infrastructure            (ffii.org)
FSF Europe                                            	  (fsfeurope.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 248 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/grass-dev/attachments/20010823/2591ef7b/attachment.bin

More information about the grass-dev mailing list