From: Simon Gerber <gesimu@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Simon Gerber via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH v2] help.c: fix autocorrect in work tree for bare repository
Date: Tue, 13 Dec 2022 10:48:23 +0100 [thread overview]
Message-ID: <CAAyHH3239rmRR5mhy-cS7XFVuXi2AnYG5nQkFcpKMd4WTfmoBg@mail.gmail.com> (raw)
In-Reply-To: <xmqqa63sqe1b.fsf@gitster.g>
On Tue, 13 Dec 2022 at 02:37, Junio C Hamano <gitster@pobox.com> wrote:
>
> "Simon Gerber via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
> > --- a/t/t9003-help-autocorrect.sh
> > +++ b/t/t9003-help-autocorrect.sh
> > @@ -60,4 +60,10 @@ test_expect_success 'autocorrect can be declined altogether' '
> > test_line_count = 1 actual
> > '
> >
> > +test_expect_success 'autocorrect works in work tree created from bare repo' '
> > + git clone --bare . bare.git &&
> > + git -C bare.git worktree add ../worktree &&
> > + git -C worktree -c help.autocorrect=immediate stauts
>
> The reason why this third line is a sufficient test is...?
>
> If "status" is invoked successfully, it would not exit with non-zero
> status as long as it correctly notices that it was invoked in a
> worktree (as opposed to the current code without your fix, which
> would say "nah, where you are running there is no worktree", that is
> incorrect), but one scenario I am a bit worried about is what if the
> tester has an entry on $PATH that has "git-static" or whatever that
> is similar enough to "status", to cause autocorrect work differently
> from the case where "git status" would be the only plausible case.
Thanks for pointing out that autocorrect could work differently for a
tester depending on what's in their path. I didn't consider that case
at all.
>
> But then we can tell such a tester "don't do that, then" ;-)
I think that's fine in this case.
>
> Let's queue the patch as-is and see what others think.
Awesome, thanks
>
> Thanks.
>
> > +'
> > +
> > test_done
>
prev parent reply other threads:[~2022-12-13 9:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 15:24 [PATCH 0/2] Fix autocorrect in work tree for bare repository Simon Gerber via GitGitGadget
2022-10-28 15:24 ` [PATCH 1/2] tests: add test case for autocorrect in work tree for bare clone Simon Gerber via GitGitGadget
2022-10-28 19:28 ` Junio C Hamano
2022-10-29 8:07 ` Simon Gerber
2022-10-28 15:24 ` [PATCH 2/2] help.c: don't call git_default_config in git_unknown_cmd_config Simon Gerber via GitGitGadget
2022-10-29 19:56 ` [PATCH v2] help.c: fix autocorrect in work tree for bare repository Simon Gerber via GitGitGadget
2022-12-12 16:38 ` Simon Gerber
2022-12-13 1:37 ` Junio C Hamano
2022-12-13 9:48 ` Simon Gerber [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=CAAyHH3239rmRR5mhy-cS7XFVuXi2AnYG5nQkFcpKMd4WTfmoBg@mail.gmail.com \
--to=gesimu@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.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.
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).