There does seem to be no technical way to handle actual conflicts. Maybe it's just that our situation is an actual conflict, which necessitates a fallback resolution, which still becomes rapidly too difficult to manually resolve. All the documents and references I've found just say stuff like "and BAM! merge problems solved!" I'd like examples, and though I usually hate tutorial videos, this tool is an excellent case for one because users have absolutely no idea what to expect - what the system looks like when it works, when it fails, etc.įor now we have to go to a system of only allowing one user to work on a scene at a time because it's too complicated to get the tool working, and we don't even understand if it IS working as expected because it isn't clear what it's supposed to be doing.
P4merge exe how to#
We spent all day yesterday trying to figure out how to use the thing. I'd like to know what the system looks like when it works, and what it looks like when it reverts to fallback behavior, and what causes it to go into fallback mode. Not allusions and insinuations about files that may exist and somewhere and might be useful.
P4merge exe full#
I would like a FULL WALKTHROUGH of setting up the tool, including EXPLICIT STATEMENTS ABOUT WHAT, IF ANY, RULES FILES NEED TO BE MODIFIED FOR THE BASIC FUNCTIONING OF THE SYSTEM. I just would like MUCH, MUCH more information. how on earth does the tool decide which cases are fallback ones? In the case of a fallback, does the tool do anything or do you just have to manually compare the yaml files? Maybe our case is a fallback case, but we couldn't get the fallback tool to launch. I tried to use the tool with a more experienced developer and it didn't seem to do anything. Couldn't hurt to also put all the arguments and their descriptions in there. Please put this information in the documentation page. As a foolish junior developer it took me several hours of googling for instructions and examples before I realized that I could run the command line option and get usage instructions for the tool. The documentation also alludes to the existence of the settings files but doesn't tell you where they are. Am I supposed to populate it with rules before it does anything? HOW does it resolve conflicts? It's supposed to use the files specified, but I don't see any information in there. There aren't even great references to this term - there are some references in Mercurial documentation, but no definition. It implies to me that no actual merge occurs. What does argument -p do? I know it says "premerge", as if everyone has heard of this word. Information is very sparse and the documentation is mysterious. I still really don't understand what the merge tool is supposed to DO.
0 kommentar(er)
