git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alban Gruin <alban.gruin@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: ag/sequencer-reduce-rewriting-todo, was Re: What's cooking in git.git (Feb 2019, #04; Sun, 24)
Date: Mon, 25 Feb 2019 19:37:30 +0100	[thread overview]
Message-ID: <2308479.hZ6iDFDOiv@andromeda> (raw)
In-Reply-To: <xmqqmumlkq3r.fsf@gitster-ct.c.googlers.com>

Hi Junio,

Le 24/02/2019 à 19:18, Junio C Hamano a écrit :
> * ag/sequencer-reduce-rewriting-todo (2019-01-29) 16 commits
>  - rebase--interactive: move transform_todo_file() to rebase--interactive.c
>  - sequencer: use edit_todo_list() in complete_action()
>  - rebase-interactive: rewrite edit_todo_list() to handle the initial edit
>  - rebase-interactive: append_todo_help() changes
>  - rebase-interactive: use todo_list_write_to_file() in edit_todo_list()
>  - sequencer: refactor skip_unnecessary_picks() to work on a todo_list
>  - sequencer: change complete_action() to use the refactored functions
>  - sequencer: make sequencer_make_script() write its script to a strbuf
>  - sequencer: refactor rearrange_squash() to work on a todo_list
>  - sequencer: refactor sequencer_add_exec_commands() to work on a todo_list
>  - sequencer: refactor check_todo_list() to work on a todo_list
>  - sequencer: introduce todo_list_write_to_file()
>  - sequencer: refactor transform_todos() to work on a todo_list
>  - sequencer: remove the 'arg' field from todo_item
>  - sequencer: make the todo_list structure public
>  - sequencer: changes in parse_insn_buffer()
> 
>  The scripted version of "git rebase -i" wrote and rewrote the todo
>  list many times during a single step of its operation, and the
>  recent C-rewrite made a faithful conversion of the logic to C.  The
>  implementation has been updated to carry necessary information
>  around in-core to avoid rewriting the same file over and over
>  unnecessarily.
> 
>  Was still being worked on, but seems to have stalled.
>  cf. <c5e3c1cc-12fa-ddf6-7008-ae47659ddc19@gmail.com>
>  cf. <97f77aca-bd19-f763-349a-de40c4b94161@talktalk.net>

I’m still working on this.  I sent a v7 shortly after the release of v2.21.0-
rc0, and I almost finished the v8.

Cheers,
Alban





  reply	other threads:[~2019-02-25 18:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-24 18:18 What's cooking in git.git (Feb 2019, #04; Sun, 24) Junio C Hamano
2019-02-25 18:37 ` Alban Gruin [this message]
2019-03-01  2:54   ` ag/sequencer-reduce-rewriting-todo, was " Junio C Hamano

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

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

  git send-email \
    --in-reply-to=2308479.hZ6iDFDOiv@andromeda \
    --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.
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 NNTP newsgroup(s).