[p4] Make a copied "branch" be a real branch

David Faison dfaison at photon.com
Wed Jul 26 15:11:03 PDT 2006

If you use the "-i" switch, you can do baseless integration between
these two locations. This approach makes for a very difficult merge
process (no way to determine when changes occurred solely in one place
or the other). 

Then again, you might be able to pass the merge task on to the offending


Since you say you know when the deed was done, you COULD create the
branch as it should have been done in the first place -  as of the last
changelist submitted prior to when the 'personal' branch was created. 

Someone would have to create a workspace based on this new branch, FLUSH
it to the depot ('flush' it because you don't want the depot files),
load it from offending user's "personal" branch, and then go through the
standard process of reconciling a workspace that has gone through
extensive edits offline.

I can't recall exactly where, but I've seen documentation on the
Perforce website that explicitly details this sort of reconciliation

David Faison

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Dan Halbert
Sent: Wednesday, July 26, 2006 4:32 PM
To: Perforce-User List
Subject: [p4] Make a copied "branch" be a real branch

Hi, I could use a little advice on the following:

Instead of creating a real branch, a user copied a directory hierarchy 
in his workspace and then added the files, something like:

    % mkdir /path/to/branch1
    % cp -r /path/to/branch1/somedir /path/to/branch2
    % p4 add /path/to/branch2/...

So the branch2/somedir/... files have no history back to branch1. He 
then edited a few of the files.

I tracked down the original branch (branch1), which he had forgotten, 
and the time when he did this. I'd like to integrate this pseudo-branch 
back into the real branch tree. I could create a new real branch and 
integrate his changes by hand, but is there an easier way to do this? I 
tried some "p4 integ -i ....." stuff with timestamp specifications in 
p4v, but couldn't quite get it to work.

Thanks a lot,
perforce-user mailing list  -  perforce-user at perforce.com

More information about the perforce-user mailing list