Timeline for answer to Git symbolic links in Windows by djs
Current License: CC BY-SA 4.0
Post Revisions
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 13, 2022 at 22:19 | history | edited | Peter Mortensen | CC BY-SA 4.0 |
Active reading [<https://github.com/msysgit/> <https://en.wikipedia.org/wiki/Git>].
|
| Dec 6, 2016 at 4:34 | comment | added | Dennis | Announced Dec 2016, Symlinks in Windows 10 is no longer an Administrator action. blogs.windows.com/buildingapps/2016/12/02/symlinks-windows-10/… | |
| Sep 24, 2016 at 19:46 | comment | added | Andrew T Finnell | @djs A User has to open a command prompt with "Run as Administrator." It is almost quite literally running as the Administrator User which completely changes the Environment. There is not a way to run 'mklink /d' as a User who also is in the Admin group. It won't UAC prompt. It will fail, always. Only two ways it works: Literally as the Administrator user (RunAs Verb), or a non-admin User with group policy change. Junctions should be the default and should be recognized by all tools. The 'security risk' is that symlinks on Windows can 'redirect' SMB shares. This is a pain and cruel. | |
| Sep 5, 2013 at 2:56 | comment | added | djs | While I do run certain machines in the Admin account, I don't follow that philosophy on my development machine. I always run as a regular user with UAC-enabled. I keep a separate console open for operations that require elevated privileges. As for getting this implemented, it comes down to someone (like you) volunteering to implement it. The msysgit developers are not known for charity... | |
| Sep 4, 2013 at 18:27 | comment | added | BrainSlugs83 | A.) currently msysgit doesn't support symlinks at all -- so why not have it detect "oh you're on vista with NTFS let me use symlinks" or "oh, you're on an OS that supports junctions with NTFS, let me use those", or "oh, you're on windows 98/fat32, let me fallback to just not having this feature and giving you a warning instead!" and then B.) Pretty much all of microsoft's dev. tools don't work right (at least not for all of their features) if you don't run them as an administrator -- everyone in IT knows that developers need to be admins on their own boxes. | |
| Aug 10, 2012 at 10:09 | comment | added | Blaisorblade | Update: for the above reasons, the issue was closed as wontfix. The discussion indicates that a fix could be accepted with some more work on the patch (say, using symlinks only if they work). | |
| May 8, 2011 at 22:06 | history | answered | djs | CC BY-SA 3.0 |