From: Phillip Wood <phillip.wood123@gmail.com>
To: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, phillip.wood@dunelm.org.uk,
"Rubén Justo" <rjusto@gmail.com>
Subject: Re: [PATCH 1/2] am: add explicit "--retry" option
Date: Mon, 10 Jun 2024 09:36:28 +0100 [thread overview]
Message-ID: <16a6b206-1733-4d64-89e6-c3e2368903ac@gmail.com> (raw)
In-Reply-To: <20240608112920.GC2966571@coredump.intra.peff.net>
Hi Peff and Junio
On 08/06/2024 12:29, Jeff King wrote:
> On Thu, Jun 06, 2024 at 09:48:52AM -0700, Junio C Hamano wrote:
>> Junio C Hamano <gitster@pobox.com> writes:
>>> Jeff King <peff@peff.net> writes:
> But I do think as a general rule we should never provide any action
> _only_ through heuristics like "is stdin a tty". We should let the user
> be explicit, and use heuristics to guess the right thing when they don't
> feel like being so.
I agree that's a good general rule to have
>>> "--retry" is a horrible word, in that it makes it sound like it will
>>> keep trying to apply the same patch over and over until it applies
>>> cleanly or something.
"retry" means "try once more", so I think it is a reasonable name for
this option. (Programs often retrying a failing operation in a loop but
then they are retrying many times.)
I haven't looked at these patches in detail so I cannot comment on the
code changes but I do think the general aim is a good one.
Best Wishes
Phillip
next prev parent reply other threads:[~2024-06-10 8:36 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 [this message]
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 ` [PATCH 0/2] dropping stdin support from test-terminal Rubén Justo
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=16a6b206-1733-4d64-89e6-c3e2368903ac@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=phillip.wood@dunelm.org.uk \
--cc=rjusto@gmail.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).