Re: [PATCH 0/2] Fix warnings on access of a remote with Windows paths
- From
Johannes Sixt <j6t@kdbg.org>
- Date
- May 22, 2017, 16:28 UTC
- Message-ID
- <1542d54f-d530-b60d-3270-d9b4e94c814d@kdbg.org>
- In-Reply-To
- <alpine.DEB.2.21.1.1705221600100.3610@virtualbox>
Am 22.05.2017 um 16:01 schrieb Johannes Schindelin:
Show 18 quoted lines
> On Mon, 22 May 2017, stefan.naewe@atlas-elektronik.com wrote: >> Am 20.05.2017 um 08:28 schrieb Johannes Sixt: >>> This small series fixes these warnings on Windows: >>> >>> C:\Temp\gittest>git fetch C:\Temp\gittest >>> warning: unable to access '.git/remotes/C:\Temp\gittest': Invalid argument >>> warning: unable to access '.git/branches/C:\Temp\gittest': Invalid argument >>> From C:\Temp\gittest >>> * branch HEAD -> FETCH_HEAD >> >> What is the exact precondition to get such a warning ? >> >> Just wondering, because I'm not able to reproduce that warning >> (with Git4win version 2.13.0.windows.1). > > I had tested this also, and came to the conclusion that only Hannes' > MSys-based custom version is affected that is much closer to git.git's > `master` than to Git for Windows' fork.
In this case, the warning occurs because I build with nd/fopen-errors.
Which explains why I observed it only recently even though I fetch from Windows paths regularly.
-- Hannes