From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Mike Hommey <mh@glandium.org>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
git@vger.kernel.org, git-for-windows@googlegroups.com
Subject: Re: [git-for-windows] Re: Revision resolution for remote-helpers?
Date: Fri, 25 Aug 2017 12:58:52 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1708251258080.7424@virtualbox> (raw)
In-Reply-To: <20170824082350.6ed6jqkn6aeylvnv@glandium.org>
Hi Mike,
On Thu, 24 Aug 2017, Mike Hommey wrote:
> On Tue, Aug 22, 2017 at 10:15:20PM +0200, Johannes Schindelin wrote:
> >
> > On Fri, 18 Aug 2017, Jonathan Nieder wrote:
> >
> > > Mike Hommey wrote[1]:
> > > > On Fri, Aug 18, 2017 at 03:06:37PM -0700, Jonathan Nieder wrote:
> > > >> Mike Hommey wrote:
> > >
> > > >>> The reason for the <helper>:: prefix is that it matches the <helper>::
> > > >>> prefix used for remote helpers.
> > > >>>
> > > >>> Now, there are a few caveats:
> > > [...]
> > > >>> - msys likes to completely fuck up command lines when they contain ::.
> > > >>> For remote helpers, the alternative that works is
> > > >>> <helper>://<host>/etc.
> > > >>
> > > >> Hm --- is there a bug already open about this (e.g. in the Git for
> > > >> Windows project or in msys) where I can read more?
> > > >
> > > > It's entirely an msys problem. Msys has weird rules to translate between
> > > > unix paths and windows paths on the command line, and botches everything
> > > > as a consequence. That's by "design".
> > > >
> > > > http://www.mingw.org/wiki/Posix_path_conversion
> > > >
> > > > (Particularly, see the last two entries)
> > > >
> > > > That only happens when calling native Windows programs from a msys
> > > > shell.
> > >
> > > Cc-ing the Git for Windows mailing list as an FYI.
> > >
> > > I have faint memories that some developers on that project have had to
> > > delve deep into Msys path modification rules. It's possible they can
> > > give us advice (e.g. about <helper>::<url> having been a bad choice of
> > > syntax in the first place :)).
> >
> > I think it is safe to assume that :: is not part of any Unix-y path. That
> > is why the MSYS2 runtime does not try to play games with it by converting
> > it to a Windows path.
> >
> > (And indeed, I just tested this, an argument of the form
> > "a::file://b/x/y/z" is not converted to a "Windows path")
>
> Note that there are people out there using msys, *and* git for windows,
> although I don't know if such people exist outside Mozilla.
Note that I am maintainer of Git for Windows, not of any setup that uses
MSys. Please do not even try to put more stuff on my plate.
Thanks,
Johannes
next prev parent reply other threads:[~2017-08-25 10:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 6:42 Revision resolution for remote-helpers? Mike Hommey
2017-08-18 12:15 ` Jeff King
2017-08-18 21:57 ` Mike Hommey
2017-08-18 22:06 ` Jonathan Nieder
2017-08-18 22:17 ` Mike Hommey
2017-08-18 22:33 ` Jonathan Nieder
2017-08-22 20:15 ` [git-for-windows] " Johannes Schindelin
2017-08-24 8:23 ` Mike Hommey
2017-08-25 10:58 ` Johannes Schindelin [this message]
2017-08-25 12:02 ` Mike Hommey
2017-09-21 1:13 ` Mike Hommey
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=alpine.DEB.2.21.1.1708251258080.7424@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git-for-windows@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=mh@glandium.org \
/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