git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Phillip Wood <phillip.wood123@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: pw/single-key-interactive (was Re: What's cooking in git.git (Feb 2022, #05; Thu, 17))
Date: Mon, 21 Feb 2022 11:14:26 +0000	[thread overview]
Message-ID: <c86845f4-b93c-d9be-cfd1-8d806fb59595@gmail.com> (raw)
In-Reply-To: <xmqqley93rkw.fsf@gitster.g>

> * pw/single-key-interactive (2022-02-16) 3 commits
>   - add -p: disable stdin buffering when interactive.singlekey is set
>   - terminal: set VMIN and VTIME in non-canonical mode
>   - terminal: pop signal handler when terminal is restored
> 
>   The single-key interactive operation used by "git add -p" has been
>   made more robust.
> 
>   Will merge to 'next'?
>   source: <pull.1146.git.1645008873.gitgitgadget@gmail.com>

Can you hold off please, I'll send a reroll in the next couple of days 
which has a additional fix for read_key_without_echo()

Thanks

Phillip

      parent reply	other threads:[~2022-02-21 17:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18  1:13 What's cooking in git.git (Feb 2022, #05; Thu, 17) Junio C Hamano
2022-02-18  2:49 ` gc/recursive-fetch-with-unused-submodules (was Re: What's cooking in git.git (Feb 2022, #05; Thu, 17)) Glen Choo
2022-02-18 16:51   ` Junio C Hamano
2022-02-18  3:28 ` What's cooking in git.git (Feb 2022, #05; Thu, 17) Elijah Newren
2022-02-18 16:51   ` Junio C Hamano
2022-02-18  5:19 ` ds/core-untrac[k]ed-cache-config (Was: Re: What's cooking in git.git (Feb 2022, #05; Thu, 17)) Elijah Newren
2022-02-18 16:50   ` ds/core-untrac[k]ed-cache-config Junio C Hamano
2022-02-19  1:53 ` en/present-despite-skipped (Re: What's cooking in git.git (Feb 2022, #05; Thu, 17)) Jonathan Nieder
2022-02-22 23:52   ` Jonathan Nieder
2022-02-23 19:39     ` Junio C Hamano
2022-02-25 16:43       ` Jonathan Nieder
2022-02-21 11:14 ` Phillip Wood [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=c86845f4-b93c-d9be-cfd1-8d806fb59595@gmail.com \
    --to=phillip.wood123@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).