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

Git-P4 Bug With Filename Case Change

From
ADAaron Dwyer <aaron.dwyer@imgtec.com>
Date
Jul 17, 2013, 22:11 UTC
Message-ID
<897B3B32-0200-4290-AA16-DCAF42923CE0@imgtec.com>
Hello Git Developers,
	We recently have moved our project from Git to Perforce and those of us who prefer Git still are using Git p4 to stay in Git land.  One of the files in our repository was renamed while still in Git, but the rename only consisted of a case change of a character in the name.  Now, on an OS X box with a case insensitive file system (not sure if that matters), one of our guys cloned from perforce with Git p4 and used @all to get all history.  When this operation is finished, the file name is in its original state, not the newer renamed state.  Perforce doesn't respect that file as being in the repository.  We noticed this after making a local Git commit and upon issuing a Git p4 submit, things go haywire with "file(s) not opened on this client" and nothing getting submitted.

Aaron Dwyer Senior Software Architect Imagination Technologies

Next: Pete Wyckoff
Message 1 of 2 in “Git-P4 Bug With Filename Case Change”
  1. Aaron DwyerJul 17, 2013
  2. Pete WyckoffJul 20, 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.