[p4] Spec depot changes

Tyler, Tom Tom.Tyler at Monster.com
Thu Jan 4 17:45:12 PST 2007


Hello!

   > Is there a way to find out who submitted the file changes [to a spec depot]?

No there's no easy way, because this information is not stored.  Spec depots tell what changed and when, but neither who nor a description indicating why.

If you *really* want to know, and if have server logging enabled and set to a high enough level, and have time to do some log analysis, then you might be able to figure it out if you have access to the server logs.  That might give you enough to at least make an educated guess to see who was running 'p4 <spec_type>' command.

For most specs, the level of configuration management afforded by the spec depot is sufficient, and I like spec depots for that purpose.  In large enterprise environments with multiple Perforce admins, though, I like to go a bit further with regular versioned files for the most important specs (protect, typemap, jobspec, and triggers).  For those I prefer to disable direct edits (e.g. with 'p4 protect'), and instead use edit/submit of a versioned file (connected to a trigger to do a 'p4 protect -i').  That way you get strong version control, and also you can put comments and whitespace into the versioned equivalents of the specs (stripping them out before doing the 'p4 protect -i').

Cheers!

Tom

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com]On Behalf Of Smith, Jeff
Sent: Tuesday, January 02, 2007 2:05 PM
To: perforce-user at perforce.com
Subject: [p4] Spec depot changes


I note that the spec depot records when changes are made but the
submitted-by field for the file revisions is empty.  Is there a way to
find out who submitted the file changes?
 
Thanks,
Jeff
 
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user


NOTICE:
This message may contain privileged or otherwise confidential information. If you are not the intended recipient, please immediately advise the sender by reply email and delete the message and any attachments without using, copying or disclosing the contents. (FE1)



More information about the perforce-user mailing list