From: Karsten Blees <karsten.blees@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, Daniel Smith <dansmith65@gmail.com>
Cc: git@vger.kernel.org, Paul Smith <paul@mad-scientist.net>,
Jeff King <peff@peff.net>,
Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
Richard Hartmann <richih@net.in.tum.de>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] git-new-workdir: add windows compatibility
Date: Tue, 26 May 2015 18:48:55 +0200 [thread overview]
Message-ID: <5564A3F7.8030305@gmail.com> (raw)
In-Reply-To: <xmqqfv6k7zp3.fsf@gitster.dls.corp.google.com>
Am 26.05.2015 um 06:03 schrieb Junio C Hamano:
> Daniel Smith <dansmith65@gmail.com> writes:
>
>> When running on Windows in MinGW, creating symbolic links via ln always
>> failed.
>>
>> Using mklink instead of ln is the recommended method of creating links on
>> Windows:
>> http://stackoverflow.com/questions/18641864/git-bash-shell-fails-to-create-symbolic-links
>>
>
> I'll defer to Windows folks if "mklink" is a sensible thing to use
> or not; I have no first-hand experience with Windows, but only heard
> that links are for admin user only or something like that, so I want
> to hear from people whose judgement on Windows matters I trust.
>
mklink:
- is not available on Windows XP
- requires special permissions
- does not work on network shares (unless enabled via 'fsutil behavior')
- only works on file systems that support reparse points (e.g. NTFS, not FAT)
AFAICT, the MSys2 symlink() implementation is pretty smart to detect these conditions and fall back to deep copy (aka 'cp -a') if symlinks are not supported.
IOW, using 'ln -s' will hopefully "just work" in the upcoming Git for Windows 2, thus trying to fix it for MSys1 / Git for Windows 1.9x is probably a lost cause.
Karsten
next prev parent reply other threads:[~2015-05-26 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADBZQ5iAKsSrdvBnFcdPcm9psaJo5B-H1zqJj0aRc+xx6cCFMQ@mail.gmail.com>
2015-05-26 4:03 ` [PATCH] git-new-workdir: add windows compatibility Junio C Hamano
2015-05-26 9:53 ` Johannes Schindelin
2015-05-26 12:20 ` Paul Smith
2015-05-26 12:35 ` Johannes Schindelin
2015-05-29 9:53 ` Michael J Gruber
2015-05-29 10:48 ` Duy Nguyen
2015-05-29 10:52 ` Johannes Schindelin
2015-05-26 16:48 ` Karsten Blees [this message]
[not found] ` <CADBZQ5hR1L7FPM_Ht00-as5eXw+PMJk1T2P3_ZiHedf0bi-H1w@mail.gmail.com>
2015-05-27 8:17 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5564A3F7.8030305@gmail.com \
--to=karsten.blees@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=Ralf.Wildenhues@gmx.de \
--cc=dansmith65@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=paul@mad-scientist.net \
--cc=peff@peff.net \
--cc=richih@net.in.tum.de \
/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).