[Top][All Lists]

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

Re: Third-party binary files, keyword expansion probs.

From: Frederic Brehm
Subject: Re: Third-party binary files, keyword expansion probs.
Date: Tue, 8 Jan 2002 17:10:48 -0500

At 16:02 -0500 1/8/02, Jack Baty wrote:
Other than the vendor branch issues, are there gotchas of which I should be
aware when managing binaries within CVS?

I have a dozen or two complete web sites under CVS control, including all of
the .gif and .jpgs. These are imported as binaries (-kb) and so far I've not
had any problems at all with this. In fact, using cvsweb, designers are
actually enjoying being able to easily view multiple previous versions of
these files right in their browsers. Sort of a "visual diff".

The main problems are:
1. merging
2. space
3. flames

If your process is such that you never have to merge two different
versions of the same image file, then you don't have to worry about
problem 1.

Problem 2 is due to the not-tuned-for-binary-data algorithm that rcs
uses to store deltas. If your files are not huge, and you have enough
disk and swap space, then this won't be a problem. You might want to
keep an eye on the size of your ,v files in the repository, though.

Problem 3 is caused by posting a question such as this to this
mailing list. You're toast!


Fred Brehm, Sarnoff Corporation, address@hidden

reply via email to

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