Re: Trimming old diffs to save space

[Paul Edwards]

"Ed Avis" <ed@membled.com> wrote in message 
news:mailman.411.1060853729.29551.bug-cvs@gnu.org...
> >To save disk space?  Which costs less than $1/GB?
>
> Some people do have disk quotas, you know...
> For me the disk space saving will not be that great - the repository
> uses only 19Mbyte altogether - but I imagine some people might want to

If your company can't afford 2 cents worth of disk space, you'd
better find another company, this one's about to go bankrupt.

> outputs.  Having outdated versions of the test suite is not that
> useful, I do not anticipate checking out old versions of the input
> data and running 'make test', nor wanting to retest older buggy
> versions of the code.  However I would like a revision history of the
> project.

zip up your archive, burn a CDROM, and if you ever want to
(you won't) find the revision history of test data (good grief),
you can always reinstall a temporary repository and look at
the log to your heart's content.

> For me the disk space saving will not be that great - the repository
> uses only 19Mbyte altogether - but I imagine some people might want to
> keep image files or other big things under version control.

So you're implementing this feature for the benefit of some
imaginary benefactor?

Wouldn't it make sense to instead fix a reported bug that
someone (everyone) actually would like to have removed from
the CVS code base?

I reported a bug recently, something about timestamps

http://www.google.com.au/groups?selm=vDqVa.21442%24OM3.2246%40news-server.bigpond.net.au&oe=UTF-8&output=gplain

As a completely random and unbiassed example of a bug that is
waiting to bite other people in the bum, including you, just waiting
for you to issue the wrong sequence of commands at the wrong
time (no pun intended).

BFN.  Paul.