From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: jim.cromie@gmail.com
Cc: git@vger.kernel.org
Subject: Re: git bisect enhancement request
Date: Fri, 14 Aug 2020 22:08:28 +0000 [thread overview]
Message-ID: <20200814220828.GP8085@camp.crustytoothpaste.net> (raw)
In-Reply-To: <CAJfuBxw2KudBPfpmVqU9VOfnvrKdczU6Us5FWvpj50T88BarHw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
On 2020-08-14 at 21:11:19, jim.cromie@gmail.com wrote:
> please teach git bisect how to use 2 separate worktrees
> for the bisection, toggling between them as bisection progresses,
> so that the end result is 2 compiled kernels,
> one broken, one good.
I'm not sure how such a thing would be implemented. Git doesn't know
until after it's checked out the tree whether a revision is good or bad,
since usually the user needs to tell it (or use git bisect run). Even
if Git alternated between the two worktrees in order, that doesn't mean
that one of them will end up being good, since Git may find the last
good revision early on, then continue to bisect and find many bad
revisions until it determines the right one.
Can you tell us more about the algorithm you'd like to see here?
--
brian m. carlson: Houston, Texas, US
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2020-08-14 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 21:11 git bisect enhancement request jim.cromie
2020-08-14 22:08 ` brian m. carlson [this message]
2020-08-14 22:25 ` Randall S. Becker
2020-08-15 13:04 ` jim.cromie
2020-08-15 22:18 ` Randall S. Becker
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=20200814220828.GP8085@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=jim.cromie@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.
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).