From: "Torsten Bögershausen" <tboegi@web.de>
To: Jeff King <peff@peff.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>,
Dmitry Bykov <pvrt74@gmail.com>,
msysgit@googlegroups.com
Subject: Re: Re: Probably a bug with "~" symbol in filenames on Windows 7 x64 in git 1.9.5
Date: Thu, 08 Jan 2015 13:59:50 +0100 [thread overview]
Message-ID: <54AE7F46.9060103@web.de> (raw)
In-Reply-To: <20150108102815.GA4806@peff.net>
On 01/08/2015 11:28 AM, Jeff King wrote:
> On Thu, Jan 08, 2015 at 11:06:18AM +0100, Johannes Schindelin wrote:
>
>> ICON~714.PNG is a valid short name for a long name (such as
>> 'icon.background.png') because it fits the shortening scheme (8.3 format,
>> the base name ends in ~<n>). As this can clash with a validly shortened
>> long name, Git for Windows refuses to check out such paths by default.
>>
>> If you want the old -- unsafe -- behavior back, just set your
>> core.protectNTFS to false (this means that you agree that the incurred
>> problems are your own responsibility and cannot be blamed on anybody else
>> ;-))
> I wonder if it is worth having a "git-only" mode for core.protectNTFS.
> Turning it off entirely would make him susceptible to GIT~1 attacks.
>
> -Peff
>
There is something more then just the "tilde" protection going on, it seems:
torstenbogershausen@TORBOGWM ~/projects/test_tilde (master)
$ ~/projects/git/msysgit/git ls-files
ICON~714.PNG
torstenbogershausen@TORBOGWM ~/projects/test_tilde (master)
$ ~/projects/git/msysgit/git status
On branch master
nothing to commit, working directory clean
torstenbogershausen@TORBOGWM ~/projects/test_tilde (master)
$ ~/projects/git/tb/git status
On branch master
nothing to commit, working directory clean
torstenbogershausen@TORBOGWM ~/projects/test_tilde (master)
$ ~/projects/git/msysgit/git --version
git version 1.9.2.msysgit.0.2273.gc47d6ec
torstenbogershausen@TORBOGWM ~/projects/test_tilde (master)
$ ~/projects/git/tb/git --version
git version 2.2.1.268.g1e6f5b2
Neither latest msygit nor latest git.git reports a problem with a single
file
within a short path.
It may be, that the '~' is not accepted in a long path or there are
"problems"
when a directory is filled with many files, but that is speculation.
Dimitry,
is there a way to make the problem reproducible for other people ?
Either a public demo-repo, or a step-by-step receipe ?
--
--
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.
You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "Git for Windows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2015-01-08 13:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 23:26 Probably a bug with "~" symbol in filenames on Windows 7 x64 in git 1.9.5 Dmitry Bykov
2015-01-07 23:35 ` Stefan Beller
2015-01-07 23:35 ` Junio C Hamano
2015-01-08 10:06 ` Johannes Schindelin
2015-01-08 10:28 ` Jeff King
2015-01-08 10:40 ` Johannes Schindelin
2015-01-08 12:59 ` Torsten Bögershausen [this message]
2015-01-08 15:58 ` [msysGit] " Johannes Schindelin
2015-01-08 16:37 ` Torsten Bögershausen
2015-01-08 19:08 ` Junio C Hamano
2015-01-08 19:42 ` Jeff King
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=54AE7F46.9060103@web.de \
--to=tboegi@web.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=msysgit@googlegroups.com \
--cc=peff@peff.net \
--cc=pvrt74@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;
as well as URLs for NNTP newsgroup(s).