Disk space usage (was: Re: UNIX version doesn't handle ^M in Entries/Repository if DOS ver used)

[Michael Gersten]

Tobias Weingartner wrote:
> And to you
> people that say "my sandbox is 100+MB, it's not practical, etc", I say
> "have you looked at the price of disk lately!?!"

I have an idea. How hard would it be to patch CVS (server side) to say
"I didn't see file,v; let me see if I see file,v.z (or file,v.gz, .bz,
.bzip, or whathaveyou), run uncompress/gunzip/bunzip, check the file
in, and then re-compress/gzip/bzip the file"?

Seems to me that defining one set of extension, compression program,
uncompress program (or uncompress flag) will completely solve this
concern of "It's getting too big".

Heck, bitkeeper is doing that, and they report that several years of
linux kernel trees get compressed down to a very reasonable size (I
think it was around 100 MB, total, for 3 years of the linux kernel
tree); if it's good enough for linux, how bad can it be for the rest
of us?

Michael
(still waiting for bitkeeper to release the final version)