[Top][All Lists]

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

Re: CVS corrupts binary files ...

From: Greg A. Woods
Subject: Re: CVS corrupts binary files ...
Date: Tue, 8 Jun 2004 17:23:34 -0400 (EDT)

[ On Saturday, June 5, 2004 at 20:52:06 (-0700), Paul Sander wrote: ]
> Subject: Re: CVS corrupts binary files ...
> Yeah, well, sending such hapless people away is easier
> than fixing the tool.

The tool is not "broken" -- I.e. there's nothing to fix!

CVS is designed _only_ for tracking changes in human written text files.

If you want to design (and implement) a new tool that does work well
with non-text files then please do so.  That'll give us yet another tool
to recommend people use when they want to.

>  Demonstrating that such support
> could be added to CVS was done in less than eight man-hours;

Nope -- it's just not possible, as you should well know.  This is a
fundamental and purposeful design limitation in CVS.  The entire concept
of concurrent editing, which is central to the design and goals of CVS,
is completely antithetical to managing binary files.

Changing the design of CVS would make it some other "VS" that is not CVS
any more.

                                                Greg A. Woods

+1 416 218-0098                  VE3TCP            RoboHack <address@hidden>
Planix, Inc. <address@hidden>          Secrets of the Weird <address@hidden>

reply via email to

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