Disk space - With perforce, every branch is a copy.Mailing patches from the GUI - again, git wins here.Don't know if it is possible in Perforce without using the command line. Stashing - Your perforce server needs to be version 2010.1 or newer to use the p4 shelve command.I squash commits like that, because they help nobody. None of that "checking in this file because it was supposed to be part of the previous checkin" rubbish.
Gitx vs sourcetree code#
I don't have to worry about that with Git. If you worked with XCode (or any editor that does not have a solid Perforce SCM plugin) offline, you know how irritating this can get. Permissions - I have lost track of the number of times I've tried to work on a file but couldn't because it was not checked out in Perforce.With git, the headache is minimized because the result of a merge in git is actually a new commit which knows who its ancestors are. Keeping track of merges - If you have one branch that is continuously receiving merges from two other branches, you know what a headache this can be with perforce.The rest of the time, git resolves stuff correctly and I save heaps of time. When Git prompts me about a conflict, it is actually a conflict. Ever since then I would rather resolve by hand when merging. Conflicts - P4Merge's auto resolve destroyed a week's worth of work once.Branching speed - git takes a few seconds at most.
Here is where I've found git to be a great benefit: No, reconcile offline work just is not the same. I also use Git because I would still like some form of version control when I'm working on code and can't connect to the server.
0 kommentar(er)
