From: "brian m. carlson" <sandals@crustytoothpaste•net>
To: K Jayatheerth <jayatheerthkulkarni2005@gmail•com>
Cc: ryenus@gmail•com, git@vger•kernel.org
Subject: Re: Re [bug] pull --prune could not delete references due to lock file already exists error
Date: Fri, 27 Jun 2025 18:59:32 +0000 [thread overview]
Message-ID: <aF7qFEfPi25_e3bq@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <20250625141849.78834-1-jayatheerthkulkarni2005@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
On 2025-06-25 at 14:18:49, K Jayatheerth wrote:
> First off thanks for reporting the bug :)
> So I cannot test this bug as my files system is case sensitive
> but to just read the code and give a thought in a direction (Assuming that the bug is recreatable)
Just so you know, on Linux, you can create a case-insensitive JFS
partition on a loopback device and on macOS, you can create a
case-insensitive APFS or HFS partition in a disk image file that can
then be mounted (I think using `hdiutil` or the directions at [0]).
I have used the former in the rare occasion that I need to test a
case-insensitive file system.
[0] https://support.apple.com/en-ca/guide/disk-utility/dskutl11888/mac
--
brian m. carlson (they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2025-06-27 18:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 12:32 [bug] pull --prune could not delete references due to lock file already exists error ryenus
2025-06-25 14:18 ` Re " K Jayatheerth
2025-06-27 18:59 ` brian m. carlson [this message]
2025-06-30 7:26 ` JAYATHEERTH K
2025-06-30 13:46 ` Karthik Nayak
2025-06-30 14:20 ` brian m. carlson
2025-06-30 21:10 ` Junio C Hamano
2025-07-01 10:31 ` Patrick Steinhardt
2025-07-01 16:14 ` Junio C Hamano
2025-07-02 8:50 ` Patrick Steinhardt
2025-07-01 8:20 ` Karthik Nayak
2025-07-02 4:50 ` Chris Torek
2025-07-02 15:37 ` Junio C Hamano
2025-07-01 0:52 ` JAYATHEERTH K
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=aF7qFEfPi25_e3bq@fruit.crustytoothpaste.net \
--to=sandals@crustytoothpaste$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=jayatheerthkulkarni2005@gmail$(echo .)com \
--cc=ryenus@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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