When comparing Gogs vs P4Merge, the Slant community recommends P4Merge for most people. In the question“What are the best merge applications for Git?” P4Merge is ranked 6th while Gogs is ranked 11th. The most important reason people chose P4Merge is:
P4Merge is free of charge.
Ranked in these QuestionsQuestion Ranking
Pro Very light
Gogs is very light and has very low minimal requirements.
Pro Excellent performance and efficiency
The fact that it's written in Go means that it has excellent performance even with little resources (less RAM for example).
Pro Simple installation
The installation process is very simple, just a binary file that needs to be run on the directory where the user wants to install Gogs
Pro Open Source
Distributed under the MIT license.
Pro Cross-platform compatibility
Gogs is written in Go, this means that Gogs can be run anywhere that Go can compile. Be it Linux, Windows or OSX.
P4Merge is free of charge.
Pro 3 way merge support
P4Merge presents merge information in 4 panes - BASE, LOCAL, REMOTE and MERGE_RESULT.
Pro Also has image diffing
For those who are working in both text based source code or files, as well as images, its nice to have the diff functionality of both present in the same product.
Pro Detects minimal changes without having a common ancestor
After a merge sometimes you have conflicts. You can resolve them by using a merge tool. You can run
git mergetool --tool-help to get more details about what tools are supported.
You will get an output like the following
git mergetool --tool=<tool> may be set to one of the following:
p4merge tortoisemerge vimdiff vimdiff2 vimdiff3
The following tools are valid, but not currently available:
araxis bc bc3 codecompare deltawalker diffmerge diffuse ecmerge emerge gvimdiff gvimdiff2 gvimdiff3 kdiff3 meld opendiff tkdiff winmerge xxdiff
Some of the tools listed above only work in a windowed environment. If run in a terminal-only session, they will fail.
Pro Cross-platform with a good Mac port
P4Merge works on Windows, Linux and OS X.
Con Only one maintainer
The project is driven by only one maintainer. The development will stop if he for some reason stops supporting the project.
Con Can not make pull requests between branches of forked repositories
Con No third party provider support
Con Supports only git
Gogs supports only the Git management system.
Con Can't filter by a user to see all their commits in one place
I want to see a single user's entire history, but clicking a user's name only shows all users' history, not just the one I clicked.
Con Directory comparison is not supported
With P4Merge it's impossible to compare two different directories to find differences.