[Bug other/15564] CVS Misplaced gcc_3_4_0_release tags

["jsm at polyomino dot org dot uk" <gcc-bugzilla at gcc dot gnu dot org>]

------- Additional Comments From jsm at polyomino dot org dot uk  2004-05-22 09:48 -------
Subject: Re:  CVS Misplaced gcc_3_4_0_release tags

On Sat, 22 May 2004, ralf_corsepius at rtems dot org wrote:

> > These look rather like files that were deleted on 3.4 branch before the
> > release was made.  As the revisions have status "dead" (i.e., deleted
> > files), I fail to see the intrinsic problem;
> 
> I don't know what you mean by "intrinsic problem", but the "user side problem"

A problem with the contents of 3.4.0 implied by the semantics of the
repository contents not agreeing with the contents of 3.4.0 as released in
tarballs.  The format of CVS repositories may not be perfectly documented,
but the manual says:

# A `dead' state means that file has been removed, or
# never added, for that revision.

I.e., dead state on 3.4 branch means the file has been removed or never
added on 3.4 branch, and dead state for 3.4.0 release means the file is
not in 3.4.0 release, and tools treating it as such are in error.

The release script would have built the tarball with cvs export
-rgcc_3_4_0_release, and it does not appear to include the files you list,
and from your bug report, it seems that cvs co is correctly interpreting
the repository as well.  If checking out from a tag and immediately
running a diff against that tag shows any diffs, that clearly indicates a
CVS bug in that different commands are interpreting the same repository
differently.  In this case, it seems to be cvs diff which is making an
incorrect interpretation.



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15564