From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: js/builtin-add-i, was Re: What's cooking in git.git (Oct 2019, #06; Thu, 24)
Date: Fri, 25 Oct 2019 16:52:03 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1910251647340.46@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqd0emfzrv.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Thu, 24 Oct 2019, Junio C Hamano wrote:
> * js/builtin-add-i (2019-08-30) 11 commits
> . built-in add -i: implement the `help` command
> . built-in add -i: use color in the main loop
> . built-in add -i: support `?` (prompt help)
> . built-in add -i: show unique prefixes of the commands
> . Add a function to determine unique prefixes for a list of strings
> . built-in add -i: implement the main loop
> . built-in add -i: color the header in the `status` command
> . built-in add -i: refresh the index before running `status`
> . built-in add -i: implement the `status` command
> . diff: export diffstat interface
> . Start to implement a built-in version of `git add --interactive`
>
> The beginning of rewriting "git add -i" in C.
>
> Expecting a reroll on top of a base with the tg/stash-refresh-index
> topic that defines an updated repo_refresh_and_write_index() helper.
> cf. <20190911175201.GA11444@cat>
FWIW I am holding off from sending this in order not to distract from
the -rc (feature freeze) phase.
I will update https://github.com/gitgitgadget/git/pull/170 in the next
minutes, for interested parties, though, with the plan to send this out
the _second_ v2.24.0 is out ;-)
Ciao,
Dscho
next prev parent reply other threads:[~2019-10-25 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 6:01 What's cooking in git.git (Oct 2019, #06; Thu, 24) Junio C Hamano
2019-10-24 21:33 ` Elijah Newren
2019-10-24 23:09 ` brian m. carlson
2019-10-25 2:51 ` Junio C Hamano
2019-10-25 14:52 ` Johannes Schindelin [this message]
2019-10-29 8:45 ` Denton Liu
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=nycvar.QRO.7.76.6.1910251647340.46@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--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).