[p4] c4: read-only/edit vs. read-write/checkin - Jorg Schaible - com.perforce.perforce-user

6 messages in com.perforce.perforce-user[p4] c4: read-only/edit vs. read-writ...

From	Sent On	Attachments
Nelson Minar	19 Jun 2000 15:28
Neil Russell	20 Jun 2000 00:22
Brad Barber	21 Jun 2000 05:41
Jorg Schaible	21 Jun 2000 10:08
Jorg Schaible	22 Jun 2000 03:28
Jeff A. Bowles	25 Jun 2000 10:49

Subject:	[p4] c4: read-only/edit vs. read-write/checkin
From:	Jorg Schaible (jorg...@db.com)
Date:	06/21/2000 10:08:49 AM
List:	com.perforce.perforce-user

Hi Brad,

this is one point where P4 and CVS have different philosophies (at least CVS in
default configuration). All CVS files in the repository are by default writable
and the developer just edits what he likes. From time to time he has to update
his sources and perform merges for the conflicts. P4 has always read-only files
in his client views and a developer must announce the change by using the edit
command (more like RCS). Conflicts will only arise, when he tries to submit his
changes and has to resolve them. Unfortunately developers used to CVS often just
remove the read-only flag from the file - this will fool the Perforce
Client/Server and may leed to inconsistencies.

Greetings, J?rg

---------------------------------------- Message History
----------------------------------------

From: bbar...@atg.com on 21/06/2000 12:41

To: caret at c-side.com cc: perforce-user at perforce.com Subject: Re: [p4] c4: read-only/edit vs. read-write/checkin

Neil,

I was thinking more from an organizational viewpoint. My guess is that most users prefer 'edit now - figure it out later' [c4] for themselves and 'let me know if you are also editing' [p4 edit] for everyone else. Which viewpoint should "win".

At 06:26 PM 6/20/00 , Neil Russell wrote:

On Tue, Jun 20, 2000 at 05:31:30PM -0400, Brad Barber wrote:

Any thoughts on why c4 is better than p4? Should I encourage everyone to use p4 and notify Perforce of intent to edit? We have about 100 developers in a rapidly changing environment.

For those users that like the way that CVS lets you do "edit now - figure it out later", then they should use c4 in front of p4. For those that are happy to do "p4 edit" before they make changes, then they can use p4 directly.

C4 just adds functionality, without disrupting the way p4 works. Users can even swap between c4 and p4 within a client workspace.