13 messages in com.perforce.perforce-userWhy are files opened for integration ...
FromSent OnAttachments
Nick...@nvidia.com18 May 1999 10:21 
Bill...@broadbase.com18 May 1999 11:06 
Patr...@manage.com18 May 1999 11:27 
Bill...@broadbase.com18 May 1999 11:27 
Patr...@manage.com18 May 1999 11:55 
Paul...@baltimore.com19 May 1999 03:20 
Nick...@nvidia.com19 May 1999 09:02 
Patr...@manage.com19 May 1999 10:05 
Will...@digintelligence.com19 May 1999 10:24 
Paul...@baltimore.com20 May 1999 01:55 
Will...@dii.com20 May 1999 09:08 
Paul...@baltimore.com20 May 1999 09:22 
Patr...@manage.com20 May 1999 09:41 
Subject:Why are files opened for integration read-only?
From:Nick...@nvidia.com (Nick@nvidia.com)
Date:05/19/1999 09:02:09 AM
List:com.perforce.perforce-user

Yes, but the problem is that if you do integrations of the scale I have done them before (16,000 files is my record... thank god for auto resolve), you don't always know that one file is messed up until you've integrated all of them and attempted a build.

I urge the folks at Perforce to:

1. Split 'p4 integrate' and 'p4 rename' into two separate commands 2. Mark files that are being updated in a depot as a result of an integrate as writeable when it is safe for the user to make subsequent changes to the integrated file before the submission.

Without #2, you run the risk of having a Perforce snapshot of broken source code, which is quite unfortunate, or you have engineers who think they have integrated files when actually they've overridden the integration with an edit.

Thanks, - -Nick

-----Original Message----- From: Jeff Bowles [mailto:Jeff.Bowles at nextcard.com] Sent: Tuesday, May 18, 1999 12:13 PM To: 'Nick Triantos'; perforce-user at perforce.com Subject: RE: Why are files opened for integration read-only?

I suspect that the reason is so users won't mess around with the files outside of the "merge" process. If the file is readonly, there is *no way* that someone can misinterpret that it shouldn't be played with without a bit of thought.

-Jeff Bowles

ps. Worse, sometimes someone does a "lazy copy" of a file ('accept theirs') but then chmod's the local copy to make a change, and can't understand why the Perforce copy doesn't reflect their changes....

-----Original Message----- From: Nick Triantos [SMTP:nick at nvidia.com] Sent: Tuesday, May 18, 1999 10:22 AM To: perforce-user at perforce.com Subject: Why are files opened for integration read-only?

Hi all,

Anyone care to venture a guess as to why files scheduled for integration are kept as read-only on the client? Often when people here integrate code, they do something that looks right during the resolve phase, but when they test the compilation, they find they need to make a minor edit.

I've told them it's safe to just change the read/write attribute of the file, since p4 will just upload their change to the server since it needs to propogate the integration, but this seems a little bit klunky.

Any ideas?

Thanks, -Nick

---- Nick Triantos Nvidia Corporation phone: 408/615-2559 3535 Monroe St. email: mailto:nick at nvidia.com Santa Clara, CA 95051 www: http://www.nvidia.com

PGP key at: http://www.triantos.com/pgpkey.html