You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, trying to clone a Mercurial repo on Windows using git-remote-hg, but it bombs out due to an attempt to create a file who's fileName contains illegal characters for a fileName on Windows (in my case the fileName contains double quotes, but single quotes, slashes, astrixes or questionMarks would have the same issue).
Now, I was wondering if this something that could be made to work properly inside git-remote-hg somehow, for example by escaping those invalid characters and perform the needed mapping, so as a user you don't have to worry about it.
Or should I just bite the bullet and try to fix my repo somehow?
Online resources tell me to configure my git repo to do a sparse checkout, excluding the files causing issues. Can look into this, but it requires to alter the git config file in your repo and since I'm still gloning, I don't have such a repo nor config file yet
The text was updated successfully, but these errors were encountered:
Hi, trying to clone a Mercurial repo on Windows using git-remote-hg, but it bombs out due to an attempt to create a file who's fileName contains illegal characters for a fileName on Windows (in my case the fileName contains double quotes, but single quotes, slashes, astrixes or questionMarks would have the same issue).
Now, I was wondering if this something that could be made to work properly inside git-remote-hg somehow, for example by escaping those invalid characters and perform the needed mapping, so as a user you don't have to worry about it.
Or should I just bite the bullet and try to fix my repo somehow?
Online resources tell me to configure my git repo to do a sparse checkout, excluding the files causing issues. Can look into this, but it requires to alter the git config file in your repo and since I'm still gloning, I don't have such a repo nor config file yet
The text was updated successfully, but these errors were encountered: