From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <code@khaugsbakk.name>
Cc: "Josh Soref" <gitgitgadget@gmail.com>,
"Harmen Stoppels" <me@harmenstoppels.nl>,
git@vger.kernel.org
Subject: Re: [PATCH v2] rebase: make warning less passive aggressive
Date: Thu, 22 Feb 2024 09:00:08 -0800 [thread overview]
Message-ID: <xmqqcysoh1t3.fsf@gitster.g> (raw)
In-Reply-To: <759cbb30-96dd-456a-baab-b9451d400dcb@app.fastmail.com> (Kristoffer Haugsbakk's message of "Thu, 22 Feb 2024 11:53:10 +0100")
"Kristoffer Haugsbakk" <code@khaugsbakk.name> writes:
> I’ve interpreted this error as: I’m not quite sure but it looks like you
> are not in the middle of a rebase? Like it can’t be completely
> sure. Maybe from a more “primitive” time, implementation-wise?[1] :)
It certainly is a good point. At least one other message in the
same command is equally less assertive, e.g.
die(_("It looks like 'git am' is in progress. Cannot rebase."));
It may have been OK to be uncertain in the earlier times back when
we did not much know what we were doing, but by now we should be
more assertive, so that the end-users can more easily complain,
saying "The command said I was not rebasing, but I was! Here is
what I did", which would hopefully be a valuable feedback for
improving the logic to diagnose what state we are in.
So, making it clear that it is a statement of a fact, or at least we
are telling the users what we _think_ the state is assertively, is a
good idea either way.
Thanks.
prev parent reply other threads:[~2024-02-22 17:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 15:23 [PATCH] rebase: make warning less passive aggressive Harmen Stoppels via GitGitGadget
2024-02-20 17:29 ` Junio C Hamano
2024-02-21 17:38 ` Michal Suchánek
2024-02-21 17:56 ` Junio C Hamano
2024-02-21 18:02 ` Junio C Hamano
2024-02-21 18:30 ` Michal Suchánek
2024-02-21 22:05 ` Jean-Noël AVILA
2024-02-21 22:46 ` Junio C Hamano
2024-02-22 1:43 ` Junio C Hamano
2024-02-22 10:01 ` Jean-Noël AVILA
2024-02-22 11:04 ` Michal Suchánek
2024-02-22 16:46 ` Junio C Hamano
2024-02-21 7:14 ` Patrick Steinhardt
2024-02-21 17:31 ` Junio C Hamano
2024-02-21 17:38 ` [PATCH v2] " Harmen Stoppels via GitGitGadget
2024-02-22 8:15 ` Patrick Steinhardt
2024-02-22 10:53 ` Kristoffer Haugsbakk
2024-02-22 17:00 ` Junio C Hamano [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=xmqqcysoh1t3.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=me@harmenstoppels.nl \
/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).