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
{{ message }}
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.
Hello, I'd like to ask for help with the issue demonstrated below.
After some time of work (under windows 7, 64bit) we get this problem, git cannot start, as the "mount" is somehow borked. Reboot of the comp helps.
This happens to only one of the guys in our team (i.e., on his computer only).
My understanding is that the "msys gets borked somehow".
I also guess that it might be connected to the problem with "dll rebase".
Perhaps the user starts some application that somehow conflicts with msys. But I'm afraid he is not willing to spend time to localize the problem; he just reboots in that case.
Are my guesses right? Is there something I could do to remove the problem?
bash.exe: warning: could not find /tmp, please create!
ERROR: HOME directory 'C:\Users\johndoe' doesn't exist!
This is an error which might be related to msysGit issue 108.
You might want to set the environment variable HOME explicitly.
Falling back to / (C:/Program Files (x86)/Git).
Welcome to Git (version 1.8.5.2-preview20131230)
Run 'git help git' to display the help index.
Run 'git help <command>' to display help for specific commands.
johndoe@W4c007 c/Users/johndow/Repo/Ger
$ ls /tmp
ls: /tmp: No such file or directory
$
The text was updated successfully, but these errors were encountered:
Hello, I'd like to ask for help with the issue demonstrated below.
After some time of work (under windows 7, 64bit) we get this problem, git cannot start, as the "mount" is somehow borked. Reboot of the comp helps.
This happens to only one of the guys in our team (i.e., on his computer only).
My understanding is that the "msys gets borked somehow".
I also guess that it might be connected to the problem with "dll rebase".
Perhaps the user starts some application that somehow conflicts with msys. But I'm afraid he is not willing to spend time to localize the problem; he just reboots in that case.
Are my guesses right? Is there something I could do to remove the problem?
The text was updated successfully, but these errors were encountered: