git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Trouble with case insensitive filesystem

From
LBLuc Bourhis <luc_j_bourhis@mac.com>
Date
May 16, 2013, 03:15 UTC
Message-ID
<075E55AB-24A4-495E-BC40-92745DE7F4AE@mac.com>
In-Reply-To
<51938E51.5060900@viscovery.net>
On 15 May 2013, at 15:32, Johannes Sixt wrote:
Show 14 quoted lines
> Am 5/15/2013 10:40, schrieb Luc Bourhis:
>> I work on a case insensitive filesystem and I have core.ignorecase set to true. 
>> ...
>> So I thought it was a job for git filter-branch, ...
>> 
>> However because of those two blobs, I have:
>> 
>> ~> git status
>> #	modified:   .../fourCircles.py
>> 
>> and git filter-branch therefore refuses to run.
> 
> Make a commit that has neither file, run git filter-branch, then throw
> away the commit with git reset --hard HEAD~.
That did not work, i.e. fourCircles remained "unmodified". Eventually, I managed by successively removing the file with "C" and then the file with "c". Then filter-branch, and then reset --hard as you suggested. Then of course, all the sha's have changed and git cvsimport can't be used for incremental updates anymore, which I knew would happen, obviously.
Thanks,
Luc J. Bourhis
 
Previous: Johannes Sixt
Message 3 of 3 in “Trouble with case insensitive filesystem”
  1. Luc BourhisMay 15, 2013
  2. Johannes SixtMay 15, 2013
  3. Luc BourhisMay 16, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.