git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
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 (Nov 2019, #01; Mon, 4)
Date: Wed, 6 Nov 2019 12:19:10 +0100 (CET)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1911061217510.46@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqzhhcxkvx.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Mon, 4 Nov 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>

I sent out v5 in
https://public-inbox.org/git/pull.170.v5.git.1572869729.gitgitgadget@gmail.com

Thanks,
Dscho

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04  5:37 What's cooking in git.git (Nov 2019, #01; Mon, 4) Junio C Hamano
2019-11-05  1:20 ` Elijah Newren
2019-11-06  2:01   ` Junio C Hamano
2019-11-06 11:19 ` Johannes Schindelin [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=nycvar.QRO.7.76.6.1911061217510.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. 
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).