[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Removing a revision but not its date&log

From: Doug Lee
Subject: Re: Removing a revision but not its date&log
Date: Wed, 24 Aug 2005 18:15:04 -0400
User-agent: Mutt/1.5.9i

You could always force commits (with descriptions) to cover the
missing source versions.  The code will not change, which will mean
very little wasted space in the repository.  See the -f flag of cvs
commit.  I'm not sure what you'd use if building the repository
directly with RCS.

On Wed, Aug 24, 2005 at 11:18:01PM +0200, Urs Thuermann wrote:
Stuart Cooper <address@hidden> writes:

> 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.

I know about diffs and space requirements.  I've been using RCS since
10 or so years and CVS since a couple of years.  I actually knew about
removing revisions from RCS files with rcs -o although I've never used
it.  I didn't want to discuss here if it's reasonable to ever do this,
for whatever reasons.

But, since the possiblity is there, I just wondered if it is possible
to keep the logs and check-in date when removing revisions.  Or more
exactly, I wanted to know if the RCS file format lets you have these
information without having the revisions file content.  I wanted to
know that because I'd like to construct RCS files and put them into my
CVS repository from old and not quite complete sources I have lying
around here in several directories, from 15-20 years ago, when I
haven't used any versioning tool.

I do know now, it's not possible.

> Inevitably you will lose some history in combining multi versions
> of your source into a new CVS repository.

Well, I don't lose what's still here, but I won't be able to add
retroactively guessed/estimated meta information of revisions I
haven't kept.

> Once your project is fully under CVS control you'll be in much
> better shape from here on in, of course.


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

ACK, quite some time ago :-)


Info-cvs mailing list

Doug Lee           address@hidden
BART Group         address@hidden
"A mailing list is a crude but effective cross between a
chain letter and a shouting match."  -Andrew Kantor

reply via email to

[Prev in Thread] Current Thread [Next in Thread]