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

Re: [RFC/ PATCH] revert: Allow arbitrary sequencer instructions

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Aug 3, 2011, 01:32 UTC
Message-ID
<CALkWK0kfOjXeuswwOvgO5eotUE89rL-X4tTtf=frGR4WdR4iAA@mail.gmail.com>
In-Reply-To
<20110802205353.GF2743@elie>
Hi Jonathan,
Jonathan Nieder writes:
Show 23 quoted lines
> Ramkumar Ramachandra wrote:
>> --- a/sequencer.h
>> +++ b/sequencer.h
>> @@ -32,6 +32,16 @@ struct replay_opts {
>>       size_t xopts_nr, xopts_alloc;
>>  };
>>
>> +struct replay_insn {
>> +     struct commit *commit;
>> +     enum replay_action action;
>> +};
>> +
>> +struct replay_insn_list {
>> +     struct replay_insn *item;
>> +     struct replay_insn_list *next;
>> +};
>
> Ah, so this allows sequences like
>
>        revert A
>        pick B
>        pick C
>        revert D
Exactly.
Show 14 quoted lines
> Nit: why isn't the list-item struct something like
>
>        struct replay_insn item;
>        struct replay_insn_list *next;
>
> which would save a little memory management and memory access
> overhead (or even
>
>        enum replay_action action;
>        struct commit *operand;
>        struct replay_insn_list *next;
>
> since every "struct replay_insn" exists in the context of an
> insn list afaict)?
Right.  Good suggestion.
> Anyway, the general idea seems good.
Nice.  Thanks for the quick early feedback.  Much appreciated.
-- Ram
Previous: Jonathan NiederNext: Ramkumar Ramachandra
Message 5 of 6 in “[GSoC update] Iterating over a stable series”
  1. Ramkumar RamachandraAug 2, 2011
  2. revert: Allow arbitrary sequencer instructionsRamkumar Ramachandra, Aug 2, 2011
  3. Christian CouderAug 2, 2011
  4. Jonathan NiederAug 2, 2011
  5. Ramkumar RamachandraAug 3, 2011
  6. Ramkumar RamachandraAug 2, 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.