Re: vger vs GitGitGadget, was Re: [PATCH v3 1/1] t0001: fix on case-insensitive filesystems

2019-06-25 Thread Junio C Hamano
Johannes Schindelin writes: >> >Again, re-sending, as something in the mail (my guess is the >> >non-ASCII character in Martin's surname) seems to upset vger so >> >much that it drops the mail unceremoniously. >> >> Hmph, but in the copy I am responding to, I can see non-ASCII >> Mart

vger vs GitGitGadget, was Re: [PATCH v3 1/1] t0001: fix on case-insensitive filesystems

2019-06-25 Thread Johannes Schindelin
Hi Junio, On Mon, 24 Jun 2019, Junio C Hamano wrote: > Johannes Schindelin writes: > > > --- > > > > Again, re-sending, as something in the mail (my guess is the > > non-ASCII character in Martin's surname) seems to upset vger so > > much that it drops the mail unceremoniously. > > H

Re: [PATCH v3 1/1] t0001: fix on case-insensitive filesystems

2019-06-24 Thread Junio C Hamano
Johannes Schindelin writes: > From: Johannes Schindelin > > On a case-insensitive filesystem, such as HFS+ or NTFS, it is possible > that the idea Bash has of the current directory differs in case from > what Git thinks it is. That's totally okay, though, and we should not > expect otherwise. >

Re: [PATCH v3 1/1] t0001: fix on case-insensitive filesystems

2019-06-24 Thread Johannes Schindelin
From: Johannes Schindelin On a case-insensitive filesystem, such as HFS+ or NTFS, it is possible that the idea Bash has of the current directory differs in case from what Git thinks it is. That's totally okay, though, and we should not expect otherwise. On Windows, for example, when you call