I'm yet to try it out, but I wonder if the problems with editing files in the linux filesystem[0] is going to be an issue with this?
[0]: https://blogs.msdn.microsoft.com/commandline/2016/11/17/do-n...
I'm yet to try it out, but I wonder if the problems with editing files in the linux filesystem[0] is going to be an issue with this?
[0]: https://blogs.msdn.microsoft.com/commandline/2016/11/17/do-n...
That was the main tripping point for me last time I tried out the WSL workflow. Mainly just because a bunch of files in our repo were apparently named in an ntfs unfriendly manner, so when I tried to merge etc. the repo would get corrupted.
Don't assume that just because the post hasn't been updated in a couple of months that it's somehow been magically "fixed" - it hasn't. In fact, its actually a really tricky problem to solve, and it'll take some time, a great deal of care, and some very well thought-out engineering before we arrive at a fix!
If/when we do fix the underlying issues we'll update this post and publish a new post announcing that the coast is clear ... until then, DO NOT CREATE/MODIFY THE LINUX FILESYSTEM USING WINDOWS TOOLS.
Thanks.