[p4] Multiple Branch management

[Jeff Grills]

I guess I never had anyone ask me to put it up.  I'm no longer with SOE,
so I don't even have access to that script anymore.  It seems like my
email is a good guide for writing that script, though.    Start with an
integrate -n between the branches, and then for all the files and all
the revisions returned, retry that specific integration to filter out
cherry-picked revisions.  Then take all the revisions that came out of
that and get their changelists.  It shouldn't be too hard.

j

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Rob Cecil
Sent: Wednesday, June 20, 2007 3:19 PM
To: perforce-user at perforce.com
Subject: [p4] Multiple Branch management

I have two branches that I'd like to be able to daily report on
regarding the integration status - if any files have been checked in
one, they need to be integrated into the other, and vice versa.
Basically a "P4BranchDiff" report that will report back to the
changelists that created the changes.

 

I'm thinking something similar to what is alluded to here: 

 

http://maillist.perforce.com/pipermail/perforce-user/2003-September/0115
10.html

 

But I cannot find this script under jgrills.

 

Thanks for your help!

Rob