Let's take a break from the regularly scheduled passive-agressive
flamefest and think about an imaginary Versioning System (iVS)
that meets the features that are being talked about. Here's the
first thought off the top of my head:
1) Use some kind of MIME file-type mapping to control settings
for locking/concurrency (so that your source files are controlled
concurrently but images use hard locks)
2) Use similar by-file-type mappings to controll the diff and
sync algorithms used (standard text diff for ascii or unicode,
something like Xdelta for your PNGs)
Such a system could be configured to behave no differently than
the current CVS, or it could be configured to always require
hard locks, or something in between.
I suppose you could set the mappings by project subdirectory too,
in case you wanted specialized control somewhere.
Ok, everybody tell me why this can't be done or why I'm talking
to the wrong list.
[ducks and runs]
Greg wrote:
>
> I.e. if you're having trouble with unmergable files and you think that
> hard locks to prevent concurrent edits are the only solution then you
> should not be using CVS. PERIOD. Please go find some other tool that
> supports hard locks in the way you desire and quit advocating for the
> impossible in CVS.
