Hi Daniel, On 2015-05-26 19:16, Daniel Smith wrote: > Thanks to everyone for reviewing my proposed patch an providing valuable > feedback. This was my first patch submission to a large open source project > like Git and the whole process was a little daunting.
Heh, yeah, it can be quite overwhelming (and this mailing list is very "male", too). Sorry! I hope, though, that it was obvious we all only wanted to be helpful? > On Tue, May 26, 2015 at 9:48 AM, Karsten Blees <karsten.bl...@gmail.com> > wrote: > >> 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. >> > > In that case, I'll abandon this patch and wait for Git for Windows 2 to > come out. Speaking of which: Could you try `git-new-workdir` with Git for Windows 2.x (developers' preview)? https://git-for-windows.github.io/#download It *might* be necessary to define the `MSYS` environment variable to `winsymlinks:nativestrict` before starting the Git Bash, to enable symlinking. It would be really good to know if that is the case so that I can do something about this in the Git for Windows installer. Ciao, Johannes -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
