If the custom merge tool correctly indicates the success of a merge resolution with its exit code, then the configuration variable ustExitCode can be set to true. When git mergetool is invoked with this tool (either through the -t or -tool option or the merge.tool configuration variable) the configured command line will be invoked with $BASE set to the name of a temporary file containing the common base for the merge, if available $LOCAL set to the name of a temporary file containing the contents of the file on the current branch $REMOTE set to the name of a temporary file containing the contents of the file to be merged, and $MERGED set to the name of the file to which the merge tool should write the result of the merge resolution. Instead of running one of the known merge tool programs, git mergetool can be customized to run an alternative program by specifying the command line to invoke in a configuration variable mergetool.cmd. Otherwise, git mergetool assumes the tool is available in PATH. For example, you can configure the absolute path to kdiff3 by setting. You can explicitly provide a full path to the tool by setting the configuration variable mergetool.path. If the configuration variable merge.tool is not set, git mergetool will pick a suitable default. If a merge resolution program is not specified, git mergetool will use the configuration variable merge.tool. Valid merge tools are: kdiff3, tkdiff, meld, xxdiff, emerge, vimdiff, gvimdiff, ecmerge, diffuse, tortoisemerge, opendiff, p4merge and araxis. t, -tool= Use the merge resolution program specified by.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |