Torsten Bögershausen writes:
> On 2014-02-01 10.14, Reuben Hawkins wrote:
>> Most case-insensitive filesystems are case-preserving. In these
>> filesystems (such as HFS+ on OS X) you can name a file Filename.txt,
>> then rename the file to FileName.txt. That file will be accessible
>> by both fi
On 2/2/14, Reuben Hawkins wrote:
>>
> This is a separate issue which core.ignorecase is sweeping under the rug.
> When you get this error message, do an 'ls' and you'll see there isn't an
> untracked file called 'FileName.txt'. There is, however, a tracked file
> called 'Filename.txt'. Because
On Sat, Feb 1, 2014 at 1:14 PM, Reuben Hawkins wrote:
> Most case-insensitive filesystems are case-preserving. In these
> filesystems (such as HFS+ on OS X) you can name a file Filename.txt,
> then rename the file to FileName.txt. That file will be accessible
> by both filenames, but the case is
On 2014-02-01 10.14, Reuben Hawkins wrote:
> Most case-insensitive filesystems are case-preserving. In these
> filesystems (such as HFS+ on OS X) you can name a file Filename.txt,
> then rename the file to FileName.txt. That file will be accessible
> by both filenames, but the case is otherwise ho
Most case-insensitive filesystems are case-preserving. In these
filesystems (such as HFS+ on OS X) you can name a file Filename.txt,
then rename the file to FileName.txt. That file will be accessible
by both filenames, but the case is otherwise honored. We don't want
to have git ignore case on th
5 matches
Mail list logo