git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Alban Gruin <alban.gruin@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: ag/sequencer-todo-updates , was Re: What's cooking in git.git (Nov 2019, #03; Tue, 19)
Date: Tue, 19 Nov 2019 19:01:13 +0100	[thread overview]
Message-ID: <3e616116-2f6f-acff-91b3-4aefc7e62653@gmail.com> (raw)
In-Reply-To: <xmqqftikxs4z.fsf@gitster-ct.c.googlers.com>

Hi Junio,

Le 19/11/2019 à 08:05, Junio C Hamano a écrit :
> * 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.

Cheers,
Alban


  parent reply	other threads:[~2019-11-19 18:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19  7:05 What's cooking in git.git (Nov 2019, #03; Tue, 19) Junio C Hamano
2019-11-19  9:38 ` Danh Doan
2019-11-20  2:52   ` Junio C Hamano
2019-11-19 17:58 ` SZEDER Gábor
2019-11-20  3:02   ` Junio C Hamano
2019-11-20 13:58     ` Derrick Stolee
2019-11-21  0:36       ` Junio C Hamano
2019-11-21 11:10         ` Derrick Stolee
2019-11-22  5:42           ` Junio C Hamano
2019-11-19 18:01 ` Alban Gruin [this message]
2019-11-19 20:41   ` ag/sequencer-todo-updates , was " Jonathan Tan
2019-11-20  3:03     ` Junio C Hamano
2019-11-21  8:17       ` Alban Gruin
2019-11-23  0:47     ` Alban Gruin
2019-11-20 23:32 ` Denton Liu
2019-11-21  0:39   ` Junio C Hamano
2019-11-23 20:35 ` Philippe Blain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3e616116-2f6f-acff-91b3-4aefc7e62653@gmail.com \
    --to=alban.gruin@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).