Geek Answers Handbook

P4 merge error, no target file (s) both in client view and in branch

First of all, I have a root stream called //// streams / main. Then I created an additional stream called //// streams / branchA, whose parent is //// streams / main. and I always worked on my own thread - branch A

Now I want to perform the integration down, from main to branch A. On my dev machine, I synchronized my local client with the latest version of branch A. Then I entered the following command (the command generated dialogue P4, Merge / Integrate, I copied it from the log window P4)

p4 merge -c 101005 -r -S //streams/BranchA -s //streams/BranchA/ ...@label _20130901

but, I got an error

 Integration errors: No target file(s) in both client and branch view. There are a total of 1 errors.

I don’t know where I was wrong, and how to fix it?

My machine for developers is WIN8, the version of the client version of P4 is 2013 March 20.

+7
perforce perforce-integrate
source share
2 answers

In my particular case there was a problem:

Using the Perforce client (version: 2014 January 15) I tried to update the stream from the parent stream.

When a filler was automatically added on the filter tab in the depot view using Merge / integrate, it was set to the source filter, but the path to the file was selected from the target, therefore, all files were filtered out.

Solutions:

  • Remove filter paths from the filter tab
  • Set a filter for the target filter (assuming paths are target objects).

NB. This particular release of the user interface looks somewhat erratic as it has several problems, many of which are related to updating the user interface or updating its state and displaying the correct menu options.

+3
source share

Well, you can look at this: Add a new folder to the repository in the P4V client

I also found that if I do not have a parent folder in my view, she does not want to do integration. For example, let's say that //streams excluded as a tree, but the subtree //streams/main turned on - then you cannot integrate it into the new branch below //streams (you cannot integrate into //streams/branchA ).

+1
source share

More articles:


All Articles