mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <>
To: Mikael Simonsson <>
Cc: Johannes Schindelin <>,
Subject: Re: Bug? git commit fileA tries to delete fileB and other oddities
Date: Tue, 17 Dec 2019 02:33:06 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Dec 16, 2019 at 09:50:33AM +0000, Mikael Simonsson wrote:

> I will try to recreate the problem with a new repository.
> So far I think I've narrowed it down to a bug introduced in git 2.20.0.
> Not buggy:
> [...]

If you can build Git from source, you might try using "git bisect" to
find the exact commit where the problem starts.

> The buggy versions all try to delete fileX when running "git commit fileA":
> % git commit fileA
> # Please enter the commit message for your changes. Lines starting
> # with '#' will be ignored, and an empty message aborts the commit.
> #
> # On branch master
> # Your branch is up to date with 'origin/master'.
> #
> # Changes to be committed:
> #       deleted:    fileX
> #       modified:   fileA
> #
> # Changes not staged for commit:

Is there anything about "fileX" and "fileA"'s names that might be
relevant? E.g., might they case-fold to the same name or something?


  reply	other threads:[~2019-12-17  7:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-14 10:39 Bug? git commit fileA tries to delete fileB and other oddities Mikael Simonsson
2019-12-15 21:09 ` Johannes Schindelin
2019-12-16  9:50   ` Mikael Simonsson
2019-12-17  7:33     ` Jeff King [this message]
2019-12-17 11:04       ` Mikael Simonsson
  -- strict thread matches above, loose matches on Subject: below --
2019-12-14 13:16 Mikael Simonsson

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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

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).