Actually I'm wrong on that count, but in an interesting way. Both CloudSponge.php and Cloudsponge.php exist and are *not* deleted in the remote repository, but on OSX only Cloudsponge.php shows up on the filesystem, yet CloudSponge.php is being reported as modified. Turns out two of our other developers are also seeing this behavior. -Chris On Wed, Dec 7, 2011 at 5:24 PM, Chris Patti <cpatti@xxxxxxxxx> wrote: > On Wed, Dec 7, 2011 at 5:03 PM, Jeff King <peff@xxxxxxxx> wrote: >> On Wed, Dec 07, 2011 at 11:54:26AM -0500, Chris Patti wrote: >> >>> OK. Let me give you a very specific series of commands, sorry about >>> the poor question / report (Not convinced it's a bug, probably pilot >>> error?) >>> >>> If my understanding of the way Git works is correct, there should be >>> NO pending diffs in a freshly cloned repository, yes? >> >> Yes. It's probably a bug, perhaps related to the case-insensitive >> filesystem (we've seen similar weird "phantom changes right after clone" >> bugs before). >> >>> 11:35][admin@Hiram-Abiff-2:~/src]$ rm -rf framework/ >>> [11:37][admin@Hiram-Abiff-2:~/src]$ >>> [11:44][admin@Hiram-Abiff-2:~/src]$ git clone >>> ssh://git.bluestatedigital.com/home/git/framework.git >>> Cloning into 'framework'... >>> remote: Counting objects: 378540, done. >>> remote: Compressing objects: 100% (100469/100469), done. >>> remote: Total 378540 (delta 261046), reused 374685 (delta 258447) >>> Receiving objects: 100% (378540/378540), 148.33 MiB | 2.08 MiB/s, done. >>> Resolving deltas: 100% (261046/261046), done. >>> [11:51][admin@Hiram-Abiff-2:~/src]$ cd framework/ >>> [11:51][admin@Hiram-Abiff-2:~/src/framework(master)]$ git diff >>> diff --git a/app/modules/Core/controllers/CloudSponge.php b/app/modules/Core/con >>> index 615a7b3..911d456 100644 >>> --- a/app/modules/Core/controllers/CloudSponge.php >>> +++ b/app/modules/Core/controllers/CloudSponge.php >> >> Are there other files in the repository that differ from this path only >> in capitalization? Can you show us the output of "git ls-files"? >> >> Is it possible to make this repo public, or at least available privately >> to git developers? >> >> You mentioned v1.7.8. Do you see the bug with other git versions? If >> not, can you try bisecting? >> >> -Peff > > Yup, you nailed it. The files in question are CloudSponge.php > (deleted) and Cloudsponge.php (still being actively maintained). > > I am seeing the same behavior with 1.7.7.4 which I backrevved to > yesterday while troubleshooting this issue. Can you suggest an older > version for me to try next? > > I'm not sure how I would git bisect in this case, I'd need to have all > the different git revs installed in order to do that right? (I'm > relatively new to git bisect, just figured it out the other day). > > Thanks, > -Chris > > -- > Christopher Patti - Geek At Large | GTalk: cpatti@xxxxxxxxx | AIM: > chrisfeohpatti | P: (260) 54PATTI > "Technology challenges art, art inspires technology." - John Lasseter, Pixar -- Christopher Patti - Geek At Large | GTalk: cpatti@xxxxxxxxx | AIM: chrisfeohpatti | P: (260) 54PATTI "Technology challenges art, art inspires technology." - John Lasseter, Pixar -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html