From: Alban Gruin <alban.gruin@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: ag/rebase-i-in-c, was Re: What's cooking in git.git (Jul 2018, #02; Wed, 18)
Date: Fri, 20 Jul 2018 19:48:05 +0200 [thread overview]
Message-ID: <e4aea192-2ed6-7715-6c66-63c873f5ce94@gmail.com> (raw)
In-Reply-To: <xmqqtvowi4l3.fsf@gitster-ct.c.googlers.com>
Hi Junio,
Le 19/07/2018 à 00:03, Junio C Hamano a écrit :
> * ag/rebase-i-in-c (2018-07-10) 13 commits
> - rebase -i: rewrite the rest of init_revisions_and_shortrevisions in C
> - rebase -i: implement the logic to initialize the variable $revision in C
> - rebase--interactive: remove unused modes and functions
> - rebase--interactive: rewrite complete_action() in C
> - sequencer: change the way skip_unnecessary_picks() returns its result
> - sequencer: refactor append_todo_help() to write its message to a buffer
> - rebase -i: rewrite checkout_onto() in C
> - rebase -i: rewrite setup_reflog_action() in C
> - sequencer: add a new function to silence a command, except if it fails
> - rebase-interactive: rewrite the edit-todo functionality in C
> - editor: add a function to launch the sequence editor
> - rebase--interactive: rewrite append_todo_help() in C
> - sequencer: make two functions and an enum from sequencer.c public
>
> Piecemeal rewrite of the remaining "rebase -i" machinery in C.
>
> Expecting a reroll.
>
> The early parts of the series seem solidifying; perhaps with a
> reroll or two, they become 'next' material?
I am working on new changes (rewriting init_basic_state(), and making
rebase--interactive a builtin), so it will probably need at least one
more reroll before being trully ready for 'next'. It’s not completely
finished yet, I hope to send it Monday or Tuesday.
Cheers,
Alban
next prev parent reply other threads:[~2018-07-20 17:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 22:03 What's cooking in git.git (Jul 2018, #02; Wed, 18) Junio C Hamano
2018-07-18 23:41 ` Stefan Beller
2018-07-19 16:33 ` Junio C Hamano
2018-07-19 6:10 ` Оля Тележная
2018-07-19 8:48 ` Eric Sunshine
2018-07-19 16:36 ` Junio C Hamano
2018-07-19 17:10 ` Elijah Newren
2018-07-20 13:42 ` ds/multi-pack-index (was Re: What's cooking in git.git (Jul 2018, #02; Wed, 18)) Derrick Stolee
2018-07-20 16:09 ` Junio C Hamano
2018-07-20 16:28 ` Derrick Stolee
2018-07-20 17:48 ` Alban Gruin [this message]
2018-07-23 18:21 ` What's cooking in git.git (Jul 2018, #02; Wed, 18) Jonathan Tan
2018-07-24 19:31 ` Junio C Hamano
2018-07-24 19:38 ` Brandon Williams
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=e4aea192-2ed6-7715-6c66-63c873f5ce94@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).