From: Johannes Sixt <j6t@kdbg.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
stefan.naewe@atlas-elektronik.com
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix warnings on access of a remote with Windows paths
Date: Mon, 22 May 2017 18:28:20 +0200 [thread overview]
Message-ID: <1542d54f-d530-b60d-3270-d9b4e94c814d@kdbg.org> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1705221600100.3610@virtualbox>
Am 22.05.2017 um 16:01 schrieb Johannes Schindelin:
> 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
next prev parent reply other threads:[~2017-05-22 16:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 6:28 [PATCH 0/2] Fix warnings on access of a remote with Windows paths Johannes Sixt
2017-05-20 6:28 ` [PATCH 1/2] mingw.h: permit arguments with side effects for is_dir_sep Johannes Sixt
2017-05-22 11:52 ` Johannes Schindelin
2017-05-20 6:28 ` [PATCH 2/2] Windows: do not treat a path with backslashes as a remote's nick name Johannes Sixt
2017-05-22 11:56 ` Johannes Schindelin
2017-05-22 11:59 ` [PATCH 0/2] Fix warnings on access of a remote with Windows paths Johannes Schindelin
2017-05-22 16:36 ` Johannes Sixt
2017-05-23 10:53 ` Johannes Schindelin
2017-05-23 18:39 ` Johannes Sixt
2017-05-22 12:38 ` stefan.naewe
2017-05-22 14:01 ` Johannes Schindelin
2017-05-22 16:28 ` Johannes Sixt [this message]
2017-05-23 10:46 ` Johannes Schindelin
2017-05-23 22:08 ` Junio C Hamano
2017-05-24 5:45 ` Johannes Sixt
2017-05-25 12:00 ` [PATCH v3 2/2] Windows: do not treat a path with backslashes as a remote's nick name Johannes Sixt
2017-05-25 23:16 ` Junio C Hamano
2017-05-22 18:58 ` [PATCH v2 1/2] mingw.h: permit arguments with side effects for is_dir_sep Johannes Sixt
2017-05-22 19:01 ` [PATCH v2 2/2] Windows: do not treat a path with backslashes as a remote's nick name Johannes Sixt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1542d54f-d530-b60d-3270-d9b4e94c814d@kdbg.org \
--to=j6t@kdbg.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=stefan.naewe@atlas-elektronik.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.