git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Re: Probably a bug with "~" symbol in filenames on Windows 7 x64 in git 1.9.5

From
Torsten Bögershausen <tboegi@web.de>
Date
Jan 8, 2015, 12:59 UTC
Message-ID
<54AE7F46.9060103@web.de>
In-Reply-To
<20150108102815.GA4806@peff.net>
On 01/08/2015 11:28 AM, Jeff King wrote:
Show 16 quoted lines
> 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.
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 7 of 11 in “Probably a bug with "~" symbol in filenames on Windows 7 x64 in git 1.9.5”
  1. Dmitry BykovJan 7, 2015
  2. Stefan BellerJan 7, 2015
  3. Junio C HamanoJan 7, 2015
  4. Johannes SchindelinJan 8, 2015
  5. Jeff KingJan 8, 2015
  6. Johannes SchindelinJan 8, 2015
  7. Torsten BögershausenJan 8, 2015
  8. Johannes SchindelinJan 8, 2015
  9. Torsten BögershausenJan 8, 2015
  10. Junio C HamanoJan 8, 2015
  11. Jeff KingJan 8, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.