Re: [PATCH] perlhack.pod - working with the Perl source

Nicholas Clark <nick@ccl4.org> writes:
>On Tue, Jun 01, 2004 at 11:36:22AM -0500, Dave Rolsky wrote:
>> On Tue, 1 Jun 2004, Rafael Garcia-Suarez wrote:
>
>> > FWIW, in Perforce you're still obliged to declare a file as being
>> > edited...
>> 
>> Heh, that's sad.
>
>It's probably a performance side effect of all state being help server side
>and nothing being stored client side. Hence the client has no idea if any
>files might have been modified (eg timestamps differ) without sending
>some data to the server and asking.

It may actually have been a request from large scale corporate users.
I know that TI's use of ClearCase used that model as with 
India/UK/Dallas/San Jose all trying to edit something at once lead 
to merge nightmares.

• [PATCH] perlhack.pod - working with the Perl source by Dave Rolsky
• Re: [PATCH] perlhack.pod - working with the Perl source by Rafael Garcia-Suarez
• Re: [PATCH] perlhack.pod - working with the Perl source by Dave Rolsky
• Re: [PATCH] perlhack.pod - working with the Perl source by Nicholas Clark
• Re: [PATCH] perlhack.pod - working with the Perl source by Nick Ing-Simmons