Bradley M . Kuhn <[EMAIL PROTECTED]> writes:
>Adam Turoff wrote:
>
>> *: Sarathy tells me that Perforce sucks at maintaining thousands of
>> anonymous checkouts, while CVS doesn't mind at all.
This is a feature of perforce that is useful - it can warn you that
you are about to change a file th
Nick Ing-Simmons wrote:
>
>
> I see no reason why the perforce changes cannot be 'checked in' to CVS
> one-by-one so that CVS builds its own representation of the change history.
I've got this working now in a program called 'vcp', I need to test
p4->cvs updates using the perl5 repository next
* Nick Ing-Simmons ([EMAIL PROTECTED]) [10 Sep 2000 06:38]:
[...]
> This is a feature of perforce that is useful - it can warn you that
> you are about to change a file that someone else is already working
> on.
As can CVS.
cheers,
--
\def\Koschei{Iain Truskett}% http://eh
