#Smartgit evaluation period ended windows
SmartGit will execute the batch file with the correct Windows working directory set but the mapping to WSL it doesn't know. Yes, I guess the batch file must somehow manage that. > 1) As we maintain multiple repos, I'd have to either use a more flexible. Hence, IMHO, we have all ingredients present and working, just the approach needs to be refined and we probably needs some SmartGit option to omit the "credential.helper". See 'git -help'.", but this can be ignored for now. SmartGit shows "git: 'credential-D:/smartgit/build/dist-templates/windows/lib/credentials.cmd' is not a git command. Will even survive WSL reboots (but will write credentials in plain text into your WSL file system). Git config -global credential.helper store Git config -global credential.helper cacheĪnd after every WSL 'boot' I ensure that Git will have cashed credentials by invoking from within WSL a To avoid the "UNC paths are not supported" error, I've mapped network drive S:\ to the root of my WSL file system and I'm opening the repository from S:\home\marc\github.priv3 My repository is located at ~/github.priv3 and I'm using following git.bat file (hacked together, for testing): symlinks can't be read (tested with Java 13):Ĭaused by: : \\wsl$\Ubuntu-20.04\home\marc\symlinks\links\link: Incorrect function.Īt java.base/.anslateToIOException(WindowsException.java:92)Īt java.base/.WindowsException.rethrowAsIOException(WindowsException.java:103)Īt java.base/.WindowsException.rethrowAsIOException(WindowsException.java:108)Īt java.base/.WindowsFileAttributeViews$Basic.readAttributes(WindowsFileAttributeViews.java:53)Īt java.base/.WindowsFileAttributeViews$Basic.readAttributes(WindowsFileAttributeViews.java:38)Īt java.base/.WindowsFileSystemProvider.readAttributes(WindowsFileSystemProvider.java:198)Īt java.base/.readAttributes(Files.java:1842).slow refreshing due to timestamp precision issues.SmartGit-specific problems when accessing \\wsl$\-paths: "credential.helper=cache" and credentials must be configured in a way that Git won't have to ask for credentials (avoid command line prompt!) => The Git credential helper must be configured to e.g. Git executable inside WSL should be used.=> a workaround is to set "core.filemode=false" for the repository executable bits are not detected, but still compared.=> "tocrlf=false" should be set for the repository => most interesting case, but works only quite limited using \\wsl$\-paths WSL2: access repository located on Linux system.WSL2: access repository located on Windows file system.
=> is this possible at all with WSL1? If so, probably issues are similar to WSL2 (see below) WSL1: access repository located on Linux system.=> why would one use WSL's Git here instead of a Windows Git? WSL1: access repository located on Windows file system.Given this topic has been posted 3 years ago and there is now WSL2, which issues are still present? According to my understanding there are following possible combinations:
0 kommentar(er)
