[p4] Reasons not to allow adding junk files to Perforce
jgrills at soe.sony.com
Fri Jun 18 11:25:40 PDT 2004
I highly support the behavior you seem to not like. But it's best to put those sorts of things in their own place. We have (where current is our mainline branch):
and so on
The //depot/studio/doc/... directory is where stuff not related to the game project goes, and //depot/swg/current/doc/... is obviously where most of the game-related documentation goes. We even add private user directories for those who ask for them, such as this:
When I was a system administrator, I found it very useful to keep much of /etc on my unix machines in source control. And we're in the process of migrating all of our live server configuration files into perforce as well.
Version control is your friend. Use it. As long as your hierarchy is laid out well, people should be able to avoid mapping in files they don't care about, and your server performance will be basically unaffected. The only concern I think you may justifiably have is disk space. Versions of files never go away - perforce only ever grows (discounting obliterate, of course).
From: perforce-user-admin at perforce.com [mailto:perforce-user-admin at perforce.com]On Behalf Of HB. Nguyen
Sent: Friday, June 18, 2004 12:22 PM
To: perforce-user at perforce.com
Subject: [p4] Reasons not to allow adding junk files to Perforce
Our management people are adding lots of stuffs that are not "Source Codes" into Perforce (ex: job descriptions, time sheets ... ).
Please give me 3 reasons to convince them not to add it to Perforce.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the perforce-user