6 messages in com.perforce.perforce-user[p4] Re: When was an open file opened
FromSent OnAttachments
Sundy, Mike09 May 2003 13:44 
Jason Williams09 May 2003 14:05 
Eric Whitcombe09 May 2003 14:10 
Jason Williams09 May 2003 14:40 
Eric Whitcombe09 May 2003 15:15 
Paul Goffin10 May 2003 01:05 
Subject:[p4] Re: When was an open file opened
From:Paul Goffin (Paul@aepsystems.com)
Date:05/10/2003 01:05:03 AM
List:com.perforce.perforce-user

There's many reasons why that can happen and has little to do with organizational practices. Say, for instance, a developer needs to tweak a Makefile (doesn't want to build the whole system, just a piece of it or something). They check out the Makefile never intending to check it back in (and in fact, they can't since write access to the tree isn't allowed).

That's one reason why I feel chasing open files is a Big Mistake.

Developers should be free to do what they want in their own workspaces and perforce helps them do this.

If you start chasing them for having files open, they'll just use attrib or chmod instead and it won't be long before your source control system is being completely ignored.

Paul.

.

******************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the postmaster at the address below. ITS-Support at aepsystems.com This footnote also confirms that this email message has been checked for the presence of computer viruses. **********************************************************************