Re: Removing a revision but not its date&log

[Stuart Cooper]

> I have no concrete use for this.  After reading the docs I could image
> that there might be a situation where you don't need to keep all
> revisions for some reason (e.g. space, completely broken revision
> which were never released and won't be used again for anything, ...)

revisions are cheap in terms of space (stored as diffs against the
previous head in the ,v file). broken revisions can be addressed
through tagging- the good stuff that was part of a stable release
is tagged, the other stuff isn't. So you can see through the top of
the output of cvs log which revs of a file are good, which ones
aren't.

> Another reason is that I am currently converting some old sources,
> where several versions of the source are distributed over some
> directories containing the date, into a CVS repository.  Theses
> sources are not complete, i.e. some versions are lost, but I roughly
> remember what was in those versions.  So I would like to create (may
> be by hand, with rcs or whatever) revision files containng
> e.g. revisions 1.1 and 1.3 and a log message for the missing 1.2.

Inevitably you will lose some history in combining multi versions
of your source into a new CVS repository. Once your project is
fully under CVS control you'll be in much better shape from here on 
in, of course.

> After looking at the structure of RCS revision files it seems it's not
> possible, but I wanted to be sure, so I asked.

Having looked at RCS revision files, you've seen that storing
versions is cheap on disk space :-).

Have fun,
Stuart.