[PATCH 0/6] Towards a generalized sequencer
From: Ramkumar Ramachandra <hidden>
Date: 2016-06-15 22:51:47
Hi, I've prepared a nicer series after Jonathan's feedback on the previous one. No new ideas; just the same ideas implemented in a more sane way. The first three patches fix some minor annoyances and don't dontribute much to the series in general. The fourth patch implements a very important idea: the ability to parse a general (action, operand) pair in the instruction sheet. The fifth patch may come as a real shocker; I was shocked myself, but I'm now convinced that this is the right way forward. Since it's only code movement, it should be very easy to review. The final patch solves a long-standing problem by introducing tighter coupling between 'git commit' and the sequencer. Thanks for lending a ear. Enjoy reading the rest! Note: I didn't know what to do with the license header in the fifth patch. I just assumed that it was some historical cruft and removed it. Ramkumar Ramachandra (6): revert: Don't remove the sequencer state on error revert: Free memory after get_message call revert: Parse instruction sheet more cautiously revert: Allow mixed pick and revert instructions sequencer: Expose API to cherry-picking machinery sequencer: Remove sequencer state after final commit builtin/commit.c | 7 +- builtin/revert.c | 1012 +-------------------------------------- sequencer.c | 962 +++++++++++++++++++++++++++++++++++++- sequencer.h | 37 ++ t/t3510-cherry-pick-sequence.sh | 91 ++++- 5 files changed, 1099 insertions(+), 1010 deletions(-) -- 1.7.6.351.gb35ac.dirty