[p4] Reasons not to allow adding junk files to Perforce

Jim Crossley jim.crossley at cptii.com
Fri Jun 18 10:45:21 PDT 2004

Revision control is not just for source code.  Any document that changes
benefits from revision control, and pretty much any business document
changes.  Perforce is so fast that it can basically be used as a shared
My only concern would be if they're submitting binary, i.e. un-diff-able
files, but most of those (often ms-office related) can be textified
rather easily.

	-----Original Message-----
	From: perforce-user-admin at perforce.com
[mailto:perforce-user-admin at perforce.com] On Behalf Of HB. Nguyen
	Sent: Friday, June 18, 2004 1:22 PM
	To: perforce-user at perforce.com
	Subject: [p4] Reasons not to allow adding junk files to Perforce
	Hi all,
	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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://maillist.perforce.com/pipermail/perforce-user/attachments/20040618/764de6ba/attachment-0008.html>

More information about the perforce-user mailing list