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:wiv...@us.itmasters.com (wiv@us.itmasters.com)
Date:11/03/2002 10:50:04 AM
List:com.perforce.perforce-user

Dan Kegel <dank at kegel.com>:

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.

Remind him that most users won't be typing //depot, they'll simply type the local path, usually relative to wherever they happen to be in their local directory tree.

That said, I'd go for option 3: Name the "depot" for the kind of work it contains (as at least one other person has pointed out), unless you never plan to have more one project. Our depots are named //dev, //docs, //qa, //users, //tools and //bld. (Aside from the organization, it makes it easy to set protections.) Oh, yeah, for display reasons, I prefer short names for the highest levels, that way I don't have to scroll sideways as much in p4Win.-Wm