git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rubén Justo" <rjusto@gmail.com>
To: Jeff King <peff@peff.net>, git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, phillip.wood@dunelm.org.uk
Subject: Re: [PATCH 0/2] dropping stdin support from test-terminal
Date: Thu, 6 Jun 2024 18:17:24 +0200	[thread overview]
Message-ID: <c2045a59-fa36-4c42-b270-0b042ff6248d@gmail.com> (raw)
In-Reply-To: <20240606081724.GA1166769@coredump.intra.peff.net>

On Thu, Jun 06, 2024 at 04:17:24AM -0400, Jeff King wrote:
> This is an alternative to Rubén's patch here:
> 
>   https://lore.kernel.org/git/d95180fc-8f8a-4e1d-987d-3aa0811be7de@gmail.com/
> 
> and instead just rips out the stdin feature of test-terminal completely.

I agree that this is a better approach.

I have no problem building my other series on this.

Thanks!

> There are two tests in t4153 that rely on it (and for which it was
> originally added), but I think the fact that we need to use
> test_terminal there indicates missing functionality in git-am.
> 
> So patch 1 fixes that, and then patch 2 simplifies test-terminal.
> 
>   [1/2]: am: add explicit "--retry" option
>   [2/2]: test-terminal: drop stdin handling
> 
>  Documentation/git-am.txt           |  8 +++++++-
>  builtin/am.c                       |  3 +++
>  t/t4153-am-resume-override-opts.sh | 14 +++++++++-----
>  t/test-terminal.perl               | 29 +++--------------------------
>  4 files changed, 22 insertions(+), 32 deletions(-)
> 
> -Peff

It has been far less than ten, laps ;-)

      parent reply	other threads:[~2024-06-06 16:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06  8:17 [PATCH 0/2] dropping stdin support from test-terminal Jeff King
2024-06-06  8:21 ` [PATCH 1/2] am: add explicit "--retry" option Jeff King
2024-06-06 16:38   ` Junio C Hamano
2024-06-06 16:48     ` Junio C Hamano
2024-06-08 11:29       ` Jeff King
2024-06-10  8:36         ` Phillip Wood
2024-06-06  8:22 ` [PATCH 2/2] test-terminal: drop stdin handling Jeff King
2024-06-06 16:14   ` Rubén Justo
2024-06-06 16:17 ` Rubén Justo [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c2045a59-fa36-4c42-b270-0b042ff6248d@gmail.com \
    --to=rjusto@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --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.
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).