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 (Aug 2018, #05; Mon, 20)
Date: Fri, 24 Aug 2018 17:30:35 +0200 [thread overview]
Message-ID: <7d10d662-2de5-56fb-31a3-d48221e5d505@gmail.com> (raw)
In-Reply-To: <xmqqsh38admf.fsf@gitster-ct.c.googlers.com>
Hi Junio,
Le 21/08/2018 à 00:15, Junio C Hamano a écrit :
> * ag/rebase-i-in-c (2018-08-10) 20 commits
> - rebase -i: move rebase--helper modes to rebase--interactive
> - rebase -i: remove git-rebase--interactive.sh
> - rebase--interactive2: rewrite the submodes of interactive rebase in C
> - rebase -i: implement the main part of interactive rebase as a builtin
> - rebase -i: rewrite init_basic_state() in C
> - rebase -i: rewrite write_basic_state() in C
> - rebase -i: rewrite the rest of init_revisions_and_shortrevisions() in C
> - rebase -i: implement the logic to initialize $revisions in C
> - rebase -i: remove unused modes and functions
> - rebase -i: rewrite complete_action() in C
> - t3404: todo list with commented-out commands only aborts
> - 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 -i: rewrite the edit-todo functionality in C
> - editor: add a function to launch the sequence editor
> - rebase -i: rewrite append_todo_help() in C
> - sequencer: make three functions and an enum from sequencer.c public
>
> Rewrite of the remaining "rebase -i" machinery in C.
>
> With "rebase -i" machinery being rewritten to C, with a different
> interface between "rebase" proper and its backends, this and the
> other topics need a bit more work to play with each other better.
I am preparing to send a new version of this patch series, but it
conflicts a bit with js/range-diff in the Makefile and in git.c. They
are not really hard to solve, though, a 3-way merge can handle this
fine. Should I rebase my work onto origin/master, or should I let you
handle this?
Cheers,
Alban
prev parent reply other threads:[~2018-08-24 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 22:15 What's cooking in git.git (Aug 2018, #05; Mon, 20) Junio C Hamano
2018-08-22 17:40 ` Junio C Hamano
2018-08-22 21:44 ` Johannes Schindelin
2018-08-22 22:52 ` Junio C Hamano
2018-08-23 14:28 ` Johannes Schindelin
2018-08-24 15:30 ` Alban Gruin [this message]
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=7d10d662-2de5-56fb-31a3-d48221e5d505@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).