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

Re: ag/sequencer-todo-updates , was Re: What's cooking in git.git (Nov 2019, #03; Tue, 19)

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 20, 2019, 03:03 UTC
Message-ID
<xmqqv9rfckq0.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20191119204146.168001-1-jonathantanmy@google.com>
Jonathan Tan <jonathantanmy@google.com> writes:
Show 18 quoted lines
>> > * ag/sequencer-todo-updates (2019-10-28) 6 commits
>> >  - SQUASH??? tentative leakfix
>> >  - sequencer: directly call pick_commits() from complete_action()
>> >  - rebase: fill `squash_onto' in get_replay_opts()
>> >  - sequencer: move the code writing total_nr on the disk to a new function
>> >  - sequencer: update `done_nr' when skipping commands in a todo list
>> >  - sequencer: update `total_nr' when adding an item to a todo list
>> > 
>> >  Reduce unnecessary reading of state variables back from the disk
>> >  during sequener operation.
>> > 
>> >  Is the leakfix patch at the tip the only thing that needs to
>> >  prepare the topic ready for 'next'?
>> > 
>> 
>> Yes, it is.
>
> I took a look at this. Some comments:

I took a look at your comments and re-read the patches and I do agree with many of your points.

Let me not merge this round to 'next' and wait for a reroll.
Thanks for stopping me.
Previous: Jonathan TanNext: Alban Gruin
Message 12 of 17 in “What's cooking in git.git (Nov 2019, #03; Tue, 19)”
  1. Junio C HamanoNov 19, 2019
  2. Danh DoanNov 19, 2019
  3. Junio C HamanoNov 20, 2019
  4. SZEDER GáborNov 19, 2019
  5. Junio C HamanoNov 20, 2019
  6. Derrick StoleeNov 20, 2019
  7. Junio C HamanoNov 21, 2019
  8. Derrick StoleeNov 21, 2019
  9. Junio C HamanoNov 22, 2019
  10. ag/sequencer-todo-updates , was Re: What's cooking in git.git (Nov 2019, #03; Tue, 19)Alban Gruin, Nov 19, 2019
  11. Jonathan TanNov 19, 2019
  12. Junio C HamanoNov 20, 2019
  13. Alban GruinNov 21, 2019
  14. Alban GruinNov 23, 2019
  15. Denton LiuNov 20, 2019
  16. Junio C HamanoNov 21, 2019
  17. Philippe BlainNov 23, 2019

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.