[p4] usefulness of a depot other than a top-level directory?

[Jeff Jensen]

I'm with Noah.  I prefer one depot per "product" (project implies work on a
product towards a release).  The product could be the "whole concept" or the
(usually sizable) components.


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Noah Salzman
Sent: Wednesday, June 07, 2006 12:39 AM
To: perforce-user at perforce.com
Subject: Re: [p4] usefulness of a depot other than a top-level directory?


On Jun 6, 2006, at 7:43 PM, Jeff Grills wrote:

> I'd say that's a Bad Idea.


I'd say exactly the opposite. Our Perforce Repository works great for us (in
both form and function) in our current layout which is something like this:

//Foo/rel1 # a major stand alone project
//Foo/rel2
//Foo/main

//Bar/rel1 # a different stand alone project
//Bar/rel2
//Bar/main

//users/jdoe # private area for individual's projects //users/jsmith

//projects/widget1  # experimental stuff that might get merged into
//projects/gadget2  # foo or bar some day

//specs # the Perforce "specs" feature


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