From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Roland Hieber <rhi@pengutronix.de>
Cc: Eric Sunshine <sunshine@sunshineco.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Git List <git@vger.kernel.org>,
Vasco Almeida <vascomalmeida@sapo.pt>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] bisect: allow to run from subdirectories
Date: Mon, 21 Jun 2021 14:45:49 +0200 [thread overview]
Message-ID: <87sg1b2xhl.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <20210621093310.eqt3ajic64pgag44@pengutronix.de>
On Mon, Jun 21 2021, Roland Hieber wrote:
> On Sun, Jun 20, 2021 at 10:10:10PM -0400, Eric Sunshine wrote:
>> On Sun, Jun 20, 2021 at 10:00 PM brian m. carlson
>> <sandals@crustytoothpaste.net> wrote:
>> > On 2021-06-21 at 00:35:49, Ævar Arnfjörð Bjarmason wrote:
>> > > On Sun, Jun 20 2021, Roland Hieber wrote:
>> > > > Currently, calling 'git bisect' from a directory other than the top
>> > > > level of a repository only comes up with an error message:
>> > > >
>> > > > You need to run this command from the toplevel of the working tree.
>> > >
>> > > How does this affect out-of-tree scripts that will be run with "git
>> > > bisect run", is the cwd set to the root as they now might expect git to
>> > > check, or whatever subdirectory you ran the "run" from?
>> >
>> > As for the idea itself, I think it's a good one assuming everything
>> > continues to work. It will certainly be more convenient for a lot of
>> > people.
>>
>> There have been multiple patches sent to the project over the years
>> with the same purpose. One problem, I believe, which has never been
>> fully addressed is what happens when the subdirectory from which
>> git-bisect is run gets deleted as part of the bisection.
>>
>> Here are a couple recent threads triggered by previous such patches
>> (but there are probably several more):
>>
>> https://lore.kernel.org/git/pull.765.git.1603271344522.gitgitgadget@gmail.com/
>> https://lore.kernel.org/git/pull.736.git.git.1584868547682.gitgitgadget@gmail.com/
>
> Ah, thanks for explaining the problem. Would a patch that adds a short
> explanatory comment in git-bisect.sh on the matter help to prevent
> people sending such patches?
Having skimmed the linked discussions I don't think the consensus is
that this shouldn't exist, but that someone who wants it should do some
research on the relevant edge cases, come up with test cases for them,
discuss the trade-offs in a commit message etc.
I for one would welcome such a feature, it's often annoyed me, it should
just work like "rebase exec" in that a "run" script should cd to the
root, but (as discussed in the linked threads) I don't see why we'd
prevent it any more than several other commands that already have this
edge case, but don't explicitly prevent this.
next prev parent reply other threads:[~2021-06-21 12:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-20 21:38 [PATCH] bisect: allow to run from subdirectories Roland Hieber
2021-06-21 0:35 ` Ævar Arnfjörð Bjarmason
2021-06-21 2:00 ` brian m. carlson
2021-06-21 2:10 ` Eric Sunshine
2021-06-21 9:33 ` Roland Hieber
2021-06-21 12:45 ` Ævar Arnfjörð Bjarmason [this message]
2021-06-21 20:02 ` Eric Sunshine
2021-06-22 15:27 ` Ævar Arnfjörð Bjarmason
2021-06-22 0:09 ` brian m. carlson
2021-06-21 3:43 ` Junio C Hamano
2021-06-23 23:40 ` Jeff King
2021-06-29 1:22 ` Junio C Hamano
2021-06-29 2:00 ` Jeff King
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=87sg1b2xhl.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rhi@pengutronix.de \
--cc=sandals@crustytoothpaste.net \
--cc=sunshine@sunshineco.com \
--cc=vascomalmeida@sapo.pt \
/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).