12 messages in com.perforce.perforce-user[p4] Why //depot?
FromSent OnAttachments
Stephen Vance01 Nov 2002 09:14 
Dan Kegel01 Nov 2002 09:15 
Robert Cowham01 Nov 2002 09:18 
Eric D. Blom01 Nov 2002 09:26 
J. Bowles01 Nov 2002 09:28 
Jeffrey Jensen01 Nov 2002 09:33 
Rich Ireland01 Nov 2002 09:43 
Steve Cogorno01 Nov 2002 10:02 
Stephen Vance01 Nov 2002 12:35 
Ed Mack01 Nov 2002 13:21 
Chuck Karish01 Nov 2002 13:38 
wiv...@us.itmasters.com03 Nov 2002 10:50 
Subject:[p4] Why //depot?
From:Stephen Vance (ste@vance.com)
Date:11/01/2002 09:14:13 AM
List:com.perforce.perforce-user

It's just the Perforce default. You couldn't create a new project/depot without 'super' privileges. In a large enough organization, the managers shouldn't have that. He probably won't like that, especially if he already wants to tell you how to run the CM details.

In normal everyday usage, it's not many extra characters. Most users use relative path names or GUIs to edit, add, delete, etc. It doesn't add characters to spec names. Most specs can be more easily created from other specs as templates, eliminating that source of typing. An environment variable (e.g. PROJROOT) can be shorter than either depot naming approach.

Steve

At Friday, 01 November 2002, Dan Kegel <dank at kegel.com> wrote:

A manager asked the question: Why add more letters to type? Why not just put our source tree at //projectname instead of //depot/projectname?

Unless I come up with a good answer, he'll make it happen.

So, why //depot? IMHO the extra path component makes it immediately clear on reading that it's a Perforce path and not a Windows UNC, say. Any other good reasons? - Dan

_______________________________________________ perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user

====================== Stephen Vance mailto:steve at vance.com http://www.vance.com