>--- Forwarded mail from [EMAIL PROTECTED]
>[EMAIL PROTECTED] on 2000.02.16 07:25:17
>>Whoa. You just said that if I want to use CVS with unmergeable files, then
>>I must supply a merge tool for them. The trouble is that no merge tool can
>>be implemented for unmergeable files, by definition. So I'm afraid that
>>suggestion isn't very helpful.
>I think he means that once a merge tool is supplied, the files are no longer
>unmergable.
I postulate that there are file formats for which no merge tool is possible.
Hence, there will never be any working merge tool available for some files.
>>Unfortunately, very few engineers doing product development seem to have
>>much interest in learning release management. They'd rather work on problems
>>that are more interesting to them and leave the code management (releases
>>and baselines) to someone else.
>This is true. Although grunts should know the basics of
>checkout-edit-build-test-merge-checkin, they shouldn't have to be configuration
>-)
>>The developers prefer the concurrency model where it's appropriate. It's
>>not much of a stretch to make it a requirement.
>Can you explain why "cvs edit -c" and "cvs watch" doesn't work in your
>environment?
Well, for one thing, "cvs edit -c" is not implmented in CVS v1.10.7, but
I can always upgrade. Is it available in 1.10.8, or do I need additional
patches. If I need patches, where do I get them?
>--- End of forwarded message from [EMAIL PROTECTED]
