From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: paul@mad-scientist.net
Cc: Junio C Hamano <gitster@pobox.com>,
Daniel Smith <dansmith65@gmail.com>,
git@vger.kernel.org, Jeff King <peff@peff.net>,
Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
Richard Hartmann <richih@net.in.tum.de>
Subject: Re: [PATCH] git-new-workdir: add windows compatibility
Date: Tue, 26 May 2015 14:35:30 +0200 [thread overview]
Message-ID: <1fb8315dfaffb91ec4925bcc458e12a2@www.dscho.org> (raw)
In-Reply-To: <1432642835.17513.22.camel@mad-scientist.net>
Hi Paul,
On 2015-05-26 14:20, Paul Smith wrote:
> On Tue, 2015-05-26 at 11:53 +0200, Johannes Schindelin wrote:
>> The biggest problem with `mklink` is that it is only supported on
>> Windows Vista and later, while I really like to keep Windows XP
>> support in Git for Windows.
>
> No, the biggest problem with mklink is that you have to have
> administrative privileges to use it... from wikipedia:
>
> http://en.wikipedia.org/wiki/NTFS_symbolic_link
It is even worse than that, as you pointed out below: administrators *can* permit non-administrators to create and use of symbolic links.
However, from a maintainer's perspective (which is my role in this thread), the compatibility problem is an even worse problem than the permissions.
>> The default security settings in Windows Vista/Windows 7 disallow
>> non-elevated administrators and all non-administrators from creating
>> symbolic links. This behavior can be changed running "secpol.msc" the
>> Local Security Policy management console (under: Security Settings
>> \Local Policies\User Rights Assignment\Create symbolic links). It can
>> be worked around by starting cmd.exe with Run as administrator option
>> or the runas command.
>
> Except even that is not so simple, as various StackOverflow questions
> and answers will show (I have to run so I can't look them up now). I
> did try to get this to work a year or so ago, and although I'm in no way
> a Windows person (so maybe someone else would have better luck) I
> couldn't get it to work.
For what it is worth, I tried my hand a couple of years ago at the project to move git-new-workdir to use the `.git` *file* and alternates mechanisms, but that does not work because you really need a separate `.git/HEAD`.
Ciao,
Johannes
next prev parent reply other threads:[~2015-05-26 13:24 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 [this message]
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
[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
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=1fb8315dfaffb91ec4925bcc458e12a2@www.dscho.org \
--to=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.
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).