In article <[EMAIL PROTECTED]>, Greg A Woods (gaw) writes:
gaw> With CVS and non-diff-able, non-patch-able files we're talking about
gaw> using a tool that's not even remotely suitable for the job at
gaw> hand.
Lets be concrete.
Say I have a software project consisteing of some number of
directories with text files in it. I keep this in CVS because I want
version tracking.
Now, someone comes along and tells me every software project needs an
icon, so this here GIF has to be part of the build. Obviously I need
to version control it in sync with the source to be able to build old
versions.
Solution 1 is to set up some other versioning system (software or
ad-hoc) to version control the image file. This gains me nothing and
costs me support overhead and possible errors compared to solution 2.
Solution 2 is to check the GIF file into CVS. This gains me simplicity
and reliability and loses me nothing compared to solution 1. I can't
diff the versions of the GIF anyway, so the fact that CVS won't add
this ability is not an issue.
QED so far as I am concerned.
--
Mail me as [EMAIL PROTECTED] _O_
|<
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
