Thanks, ran into this exact issue because some developers use GNU/Linux (ext3 or ext4), where filenames are NOT case-sensitive, and I use Mac OS X, where filenames ARE case-sensitive. Thus, only OS X users were getting the git error. But once it happens you cannot push any code at all, no matter what branch you're in until it is fixed remotely.
In other words, you could have wip/FOO and wip/foo/bar exist perfectly fine on an ext3/4 Linux system, because FOO is a file and "foo" is a folder, but it would break on mac os x.
Thanks, ran into this exact issue because some developers use GNU/Linux (ext3 or ext4), where filenames are NOT case-sensitive, and I use Mac OS X, where filenames ARE case-sensitive. Thus, only OS X users were getting the git error. But once it happens you cannot push any code at all, no matter what branch you're in until it is fixed remotely.
In other words, you could have wip/FOO and wip/foo/bar exist perfectly fine on an ext3/4 Linux system, because FOO is a file and "foo" is a folder, but it would break on mac os x.