[cvsnt] How to deal with too large CVS database?
Bo Berglund
Bo.Berglund at system3r.se
Wed Nov 9 11:47:32 GMT 2005
There is an cvs admin command to delete specific revisions of a file:
cvs admin -o <range of revisions to delete> filename
But the command cannot remove revisions with branches on them.
Dangerous but if done in a copy of your repository then you could experiment
a bit and see how it works.
/Bo
-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Pedja Supurovic
Sent: den 9 november 2005 10:44
To: cvsnt at cvsnt.org
Subject: [cvsnt] How to deal with too large CVS database?
Our source got far too big so we are looking for an solution to deal
with it.
We had an idea to lock currnet repository, make it read only and create
new one with packed database which contains only the last versions of
each file in source. That would allow us to access previous versions but
continue development with fresh, and small source database.
We cannot find way to achieve this but preserve file version numbers
within source (if we create new repository and put new source in it,
file version numbers are reset). Is it possible at all to preserv
version numbers or pack database by keeping only the last version of
each file within source?
Pedja
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
More information about the cvsnt
mailing list