In the summer of 2011, I wrote a sequencer for git. Ever since, people have been struggling to explain what exactly it is in plain english, so I'll rectify that now. The vision was to create a framework that could sequence arbitrary git operations, and git abort or git continue after interruptions (conflicts, for instance). Then, various commands that follow this start-interrupt-continue workflow can simply call into this framework instead of implementing their own git foo --abort and git foo --continue. An example of a command that follows this workflow is git rebase --interactive. Unfort...