19 messages in com.perforce.perforce-user[p4] Reasons not to allow adding junk...
FromSent OnAttachments
HB. Nguyen18 Jun 2004 10:21 
Hoff, Todd18 Jun 2004 10:44 
Jim Crossley18 Jun 2004 10:44 
Ivey, William18 Jun 2004 10:47 
Janulewicz, Matthew18 Jun 2004 10:50 
Cris Holdorph18 Jun 2004 10:57 
Jeff Younker18 Jun 2004 11:23 
Todd Short18 Jun 2004 11:23 
Grills, Jeff18 Jun 2004 11:25 
Dave Birkhead18 Jun 2004 11:25 
Janulewicz, Matthew18 Jun 2004 11:42 
Jeff Younker18 Jun 2004 12:04 
Rajul Vora18 Jun 2004 12:17 
Mark Harrison18 Jun 2004 13:18 
Jason Williams18 Jun 2004 14:08 
Ivey, William18 Jun 2004 14:30 
Arnt Gulbrandsen20 Jun 2004 05:29 
Chuck Karish20 Jun 2004 12:43 
Mark Harrison21 Jun 2004 10:25 
Subject:[p4] Reasons not to allow adding junk files to Perforce
From:Jim Crossley (jim.@cptii.com)
Date:06/18/2004 10:44:59 AM
List:com.perforce.perforce-user

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 filesystem.

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.

Jim

-----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 Perforce. Thanks