git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Devste Devste <devstemail@gmail.com>
To: git@vger.kernel.org
Subject: git bisect stuck - --force flag required for checkout
Date: Thu, 21 Dec 2023 11:47:57 +0100	[thread overview]
Message-ID: <CANM0SV3SEF28QJ2V0Q9ydp8yDbL8TDc1m871oxOB=UtwF1TtxQ@mail.gmail.com> (raw)

Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)
add file Foo.txt to .git and commit
add some commits with any changes to other files, as this is needed
for reproduction
run: git config core.ignorecase false
rename Foo.txt to foo.txt and commit
add some commits with any changes to other files, as this is needed
for reproduction
run: git bisect start && git bisect bad
eventually, when running "git bisect good" (or bad) you will get an error:
>error: The following untracked working tree files would be overwritten by checkout:
>Foo.php

Anything else you want to add:
git bisect good/bad needs to have support for a "--force" flag, which
is passed to the git checkout it runs internally
At the moment git bisect cannot be used on Windows, as there is no way
to continue the bisect from here.
Changing the "git config core.ignorecase true" temporarily is not an
option, as this will introduce a variety of other bugs,
which, on Windows, eventually will require you to completely delete
and reclone the repo, as Windows file paths are case-insensitive

[System Info]
git version:
git version 2.39.1.windows.1
cpu: i686
built from commit: b03dafd9c26b06c92d509a07ab01b01e6d0d85ee
sizeof-long: 4
sizeof-size_t: 4
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Windows 10.0
compiler info: gnuc: 12.2
libc info: no libc information available


[Enabled Hooks]


             reply	other threads:[~2023-12-21 10:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21 10:47 Devste Devste [this message]
2023-12-21 12:22 ` git bisect stuck - --force flag required for checkout brian m. carlson

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='CANM0SV3SEF28QJ2V0Q9ydp8yDbL8TDc1m871oxOB=UtwF1TtxQ@mail.gmail.com' \
    --to=devstemail@gmail.com \
    --cc=git@vger.kernel.org \
    /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).