Your use of the packages on this site means you understand they are not supported or guaranteed in any way. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.įortunately, distribution rights do not apply for internal use. If you are an organization using Chocolatey, we want your experience to be fully reliable.ĭue to the nature of this publicly offered repository, reliability cannot be guaranteed.
Human moderators who give final review and sign off. Security, consistency, and quality checking. ModerationĮvery version of each package undergoes a rigorous moderation process before it goes live that typically includes: This is the result: Ĭmd = "/c/Program\\ Files/WinMerge/WinMergeU.Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community. And lastly, the options for mergetool are improved. The path to the WinMergeU.exe is adjusted. Since I am happy with the Git internal diff tool, I will leave out that configuration. To apply this for my machine and scenario, I made some adjustments. Ĭmd = "/c/Program\\ Files\\ \\(x86\\)/WinMerge/WinMergeU.exe" -u -e -dl \"Local\" -dr \"Remote\" $LOCAL $REMOTE $MERGEDĬmd = "/c/Program\\ Files\\ \\(x86\\)/WinMerge/WinMergeU.exe" -u -e $LOCAL $REMOTEĪs was pointed out in the comments, this will work for diff but can potentially provide some trouble for merge. 
In my research I came across this helpful Gist by Shawn Dumas. Today I wanted to set up WinMerge as default mergetool for Git.
0 kommentar(er)
