I've been using Perforce for a number of years. I'd like to switch to using git for my personal code, but all of the git tutorials that I've seen either assume that you'e a complete source control n00b (which makes them incredibly tedious) or that you're used to svn (which I'm not).
I know p4, and I also understand the idea behind a distributed source control system (so I don't need a sales pitch, thanks). What I'd like is a translation table from p4 command to equivalent git commands, as well as the "can't live without" commands that have no p4 equivalent.
Since I suspect every p4 user uses a different subset of p4, here are some of the things I regularly do in p4 that I'd like to be able to do in git that aren't immediately obvious from the docs I've looked at:
- create multiple pending changelists in a single client. (
p4 change) - edit a pending changelist. (also
p4 change) - see a list of all of my pending changelists (
p4 changes -s pending) - list of all of the changed files in my client (
p4 opened) or in a pending changelist (p4 describe) - see a diff of a pending changelist (I use a wrapper script for this which uses
p4 diffandp4 describe) - for a given file, see which submitted changelists affected which lines (
p4 annotate) - for a given file, see a list of the descriptions of the changelists that affected the file (
p4 log) - submit a pending changelist (
p4 submit -c) - abort a pending changelist (
p4 revert)
A lot of these revolve around "changelists". "changelist" is p4 terminology. What's the git equivalent term?
It sounds like branches might be what git users use in place of what p4 calls changelists. A bit confusing, since p4 also has something called a branch though they seem to be only vaguely related