From: "Torsten Bögershausen" <tboegi@web.de>
To: "Paweł Redzyński" <pawelredzynski@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Question on case insensitive systems.
Date: Fri, 13 Mar 2020 16:22:23 +0100 [thread overview]
Message-ID: <20200313152223.4glbokvfcmexrx4n@tb-raspi4> (raw)
In-Reply-To: <CAOTQ0KvpO5iVFsMqz5WPZd8uEd9_SRxQvznvEEB05jnTTWXBBg@mail.gmail.com>
On Fri, Mar 13, 2020 at 01:05:46PM +0100, Paweł Redzyński wrote:
> Hello,
> I noticed that check for filename collision on case insensitive
> systems happen only upon clone:
> https://github.com/git/git/blob/c522f061d551c9bb8684a7c3859b2ece4499b56b/entry.c#L499
> and
> https://github.com/git/git/blob/c522f061d551c9bb8684a7c3859b2ece4499b56b/unpack-trees.c#L445
>
> What if collision exists on some commit that is checked out only after clone?
The OS will overwrite e.g. the content of "FILE.TXT" with "file.txt" if
both exist in the repo.
(Or the other way around)
As a result, "FILE.TXT" would have the contents of "file.txt" which is
typically different, and Git will report "FILE.TXT" as "modified".
>
> Is this behavior intentional (eg. for performance reasons)?
That depends on the definition of "performance".
The Git-developpers have not yet implemented a better solution,
since most of them do such things in their spare time.
As a consequence, we haven't been able to measure the performance
on a computer running Git.
>If its a bug, can I volunteer to solve it?
I would call it a feature, worth to be implemented.
And of course, you are wellcome to solve it.
I (and probably many others) are happy to help with code-reviews
and other tips, hints, suggestions.
> Best regards
> Paweł
prev parent reply other threads:[~2020-03-13 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 12:05 Question on case insensitive systems Paweł Redzyński
2020-03-13 15:22 ` Torsten Bögershausen [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=20200313152223.4glbokvfcmexrx4n@tb-raspi4 \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=pawelredzynski@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).