Re: Probably a bug with "~" symbol in filenames on Windows 7 x64 in git 1.9.5
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Jan 8, 2015, 10:40 UTC
- Message-ID
- <alpine.DEB.1.00.1501081140070.21312@s15462909.onlinehome-server.info>
- In-Reply-To
- <20150108102815.GA4806@peff.net>
Hi Peff,
On Thu, 8 Jan 2015, Jeff King wrote:
Show 14 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.
That is a good idea!
Ciao, Dscho