Bernhard Reiter bernhard at intevation.de
Thu Aug 23 12:48:33 EDT 2001

On Thu, Aug 23, 2001 at 06:34:20PM +0200, Markus Neteler wrote:
> On Thu, Aug 23, 2001 at 06:13:19PM +0200, Bernhard Reiter wrote:
> > Markus:
> > 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 
> > revisions. 
> Well, if the non-branch-tag elimination also removed this tag description
> (while keeping the sources) I feel that neither "cvs log" nor "cvs status"
> can see anything (as it is removed). Hopefully I am wrong.

You are right. But this is not a problem.
Look from cvs perspective: CVS usually keeps one file in the
repository per source file. This file has a header which contains roughly
what can be seen with cvs status. Then there are all source
revisions in this file. You can get information about then with log.

> It is not clear to me *when* (Date) the non-branch tag
> "releasebranch_11_april_2001_5_0_0" has been applied. This may reduce the
> number of log-lines to analyse (at time 250k lines).

There is probably no way to find out as "cvs history" does not log it.

> If
>  - we know when the non-branch tag was applied
>  - we have a version shortly before the application
> we might find out which code was removed due to the non-branch tag-removal?

Code will be there but maybe not on the branch.
I only removed the non-branch tag from files which were not on the branch.

We should be save. My suggestion: Make a pre-release and check the
names and numbers of the files in the tarball with the last
prerelease and compare...
-------------- 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/62aaffa4/attachment.bin

More information about the grass-dev mailing list