git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 0/6] Towards a generalized sequencer

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Aug 11, 2011, 18:51 UTC
Message-ID
<1313088705-32222-1-git-send-email-artagnon@gmail.com>
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
Next: Ramkumar Ramachandra
Message 1 of 31 in “Towards a generalized sequencer”
  1. 0/6 Towards a generalized sequencerRamkumar Ramachandra, Aug 11, 2011
  2. 1/6 revert: Don't remove the sequencer state on errorRamkumar Ramachandra, Aug 11, 2011
  3. Jonathan NiederAug 11, 2011
  4. Ramkumar RamachandraAug 13, 2011
  5. 2/6 revert: Free memory after get_message callRamkumar Ramachandra, Aug 11, 2011
  6. Jonathan NiederAug 11, 2011
  7. Ramkumar RamachandraAug 12, 2011
  8. 3/6 revert: Parse instruction sheet more cautiouslyRamkumar Ramachandra, Aug 11, 2011
  9. Jonathan NiederAug 11, 2011
  10. 4/6 revert: Allow mixed pick and revert instructionsRamkumar Ramachandra, Aug 11, 2011
  11. Jonathan NiederAug 11, 2011
  12. Ramkumar RamachandraAug 13, 2011
  13. 5/6 sequencer: Expose API to cherry-picking machineryRamkumar Ramachandra, Aug 11, 2011
  14. Jonathan NiederAug 11, 2011
  15. Jonathan NiederAug 11, 2011
  16. Junio C HamanoAug 11, 2011
  17. Ramkumar RamachandraAug 13, 2011
  18. Daniel BarkalowAug 13, 2011
  19. Ramkumar RamachandraAug 13, 2011
  20. Reusing changes after renaming a file (Re: [PATCH 5/6] sequencer: Expose API to cherry-picking machinery)Jonathan Nieder, Aug 13, 2011
  21. Ramkumar RamachandraAug 13, 2011
  22. Jonathan NiederAug 13, 2011
  23. Jonathan NiederAug 13, 2011
  24. Ramkumar RamachandraAug 13, 2011
  25. 6/6 sequencer: Remove sequencer state after final commitRamkumar Ramachandra, Aug 11, 2011
  26. Jonathan NiederAug 11, 2011
  27. Ramkumar RamachandraAug 12, 2011
  28. Jonathan NiederAug 11, 2011
  29. Ramkumar RamachandraAug 12, 2011
  30. Jonathan NiederAug 12, 2011
  31. Ramkumar RamachandraAug 12, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.