git@vger.kernel.org list mirror (unofficial, 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, Carlo Arenas <carenas@gmail.com>,
	Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: js/use-builtin-add-i, was Re: What's cooking in git.git (May 2022, #06; Fri, 20)
Date: Sun, 22 May 2022 00:02:39 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.2205212352540.352@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqmtfbcoaa.fsf@gitster.g>

Hi Junio,

On Sat, 21 May 2022, Junio C Hamano wrote:

> * js/use-builtin-add-i (2021-12-01) 2 commits
>  - add -i: default to the built-in implementation
>  - t2016: require the PERL prereq only when necessary
>
>  "git add -i" was rewritten in C some time ago and has been in
>  testing; the reimplementation is now exposed to general public by
>  default.
>
>  On hold.
>
>  What's the status of the "known breakage"?
>  Are we ready to switch if we wanted to?
>  There are known breakages on macOS.
>  cf. <nycvar.QRO.7.76.6.2112021832060.63@tvgsbejvaqbjf.bet>
>  source: <pull.1087.git.1638281655.gitgitgadget@gmail.com>

As per
https://lore.kernel.org/git/CAPUEspg1cJC_UwjJFx-jnzWsascY++S3UgM1UCLRcnK_Mv2wOg@mail.gmail.com/,
I believe that the macOS breakages have been confirmed to be addressed by
`pw/single-key-interactive` (which was merged in 32f3ac26e03, i.e. it was
included in v2.36.0).

Therefore, right now might be a good time to advance the
`js/use-builtin-add-i` series.

Thanks,
Dscho

  parent reply	other threads:[~2022-05-21 22:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-21  7:55 What's cooking in git.git (May 2022, #06; Fri, 20) Junio C Hamano
2022-05-21 18:07 ` ds/bundle-uri (was Re: What's cooking in git.git (May 2022, #06; Fri, 20)) Derrick Stolee
2022-05-23 20:09   ` Junio C Hamano
2022-05-21 22:02 ` Johannes Schindelin [this message]
2022-05-23 17:41   ` js/use-builtin-add-i, was Re: What's cooking in git.git (May 2022, #06; Fri, 20) 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

  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.2205212352540.352@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=carenas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=phillip.wood@dunelm.org.uk \
    /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).