git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH 1/1] Avoid illegal filenames when building Documentation on NTFS
Date: Wed, 10 Jul 2019 12:08:26 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1907101202330.46@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqef2zw9op.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Tue, 9 Jul 2019, Junio C Hamano wrote:

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > In addition, your `+` scheme will break on Windows once it uses
> > `git.exe` or any other non-MSYS2 helper...
>
> I am not sure what you mean here.  Is your git.exe disabled not to
> be able to do this: "git.exe add hello+kitty.txt"?  I think that is
> a more grave problem, and not limited to the Makefile in the
> Documentation/ directory.

A `+` character is not allowed as part of a file name on Windows.
Therefore, it is not so much `git.exe`'s problem, as the Git build's
problem that it uses such an illegal character.

It _just happens_ to work at the moment, by virtue of Git for Windows'
SDK _by happenstance_ using only MSYS2-programs to manipulate those
files in question. And MSYS2 programs use a derivative of the Cygwin
runtime which uses a dirty trick to pretend _to MSYS2 programs only_
that `+` (and other characters that are equally illegal in file names on
Windows) can be used for file names: those characters are mapped into
a private page of the Unicode range.

Needless to say, only MSYS2 programs know how to deal with such file
names. If you ever use any program that is not based on the MSYS2/Cygwin
runtime (such as `git.exe`), things will break.

This strikes me as a fragile setup, hence my attempt to fix it.

Ciao,
Dscho

  reply	other threads:[~2019-07-10 10:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04  9:14 [PATCH 0/1] windows: avoid illegal filenames during a build Johannes Schindelin via GitGitGadget
2019-07-04  9:14 ` [PATCH 1/1] Avoid illegal filenames when building Documentation on NTFS Johannes Schindelin via GitGitGadget
2019-07-08 19:23   ` Junio C Hamano
2019-07-09 13:27     ` Johannes Schindelin
2019-07-09 14:43       ` Junio C Hamano
2019-07-10 10:08         ` Johannes Schindelin [this message]
2019-07-10 18:26         ` Junio C Hamano
2019-07-10 20:35           ` Johannes Schindelin

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=nycvar.QRO.7.76.6.1907101202330.46@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).