From: "Philip Oakley" <philipoakley@iee.org>
To: <noloader@gmail.com>, "Git List" <git@vger.kernel.org>
Subject: Re: Crash when clone includes magic filenames on Windows
Date: Sat, 10 Feb 2018 10:29:40 -0000 [thread overview]
Message-ID: <BD73CAACE3734EE89EE1CFBE1DC55FEC@PhilipOakley> (raw)
In-Reply-To: CAH8yC8nodewYm-J3ye5Lnq-Zf9JziejL8L3TxTEwVoq8hD--HA@mail.gmail.com
From: "Jeffrey Walton" <noloader@gmail.com>
> Hi Everyone,
>
> I'm seeing this issue on Windows: https://pastebin.com/YfB25E4T . It
> seems the filename AUX is the culprit. Also see
> https://blogs.msdn.microsoft.com/oldnewthing/20031022-00/?p=42073 .
> (Thanks to Milleneumbug on Stack Overflow).
>
> I did not name the file, someone else did. I doubt the filename will be
> changed.
>
> Searching is not turning up much information:
> https://www.google.com/search?q=git+"magic+filenames"+windows
>
> Does anyone know how to sidestep the issue on Windows?
>
> Jeff
>
This comes up on the Git-for-Windows (GfW) issues fairly often
https://github.com/git-for-windows/git/issues.
The fetch part of the clone is sucessful, but the final checkout step fails
when the AUX (or any other prohibited filename - that's proper cabkward
compatibility for you) is to be checked out then the file system (FS)
refuses and the checkout 'fails. You do however have the full repo locally.
The trick is probably then to set up a sparse checkout so the AUX is never
included on the FS.
However it is an open 'up-for-grabs' project to add such a check in GfW.
Philip
next prev parent reply other threads:[~2018-02-10 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 8:55 Crash when clone includes magic filenames on Windows Jeffrey Walton
2018-02-10 9:31 ` Torsten Bögershausen
2018-02-10 9:42 ` Jeffrey Walton
2018-02-10 10:29 ` Philip Oakley [this message]
2018-02-10 15:27 ` Philip Oakley
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=BD73CAACE3734EE89EE1CFBE1DC55FEC@PhilipOakley \
--to=philipoakley@iee.org \
--cc=git@vger.kernel.org \
--cc=noloader@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox