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
git commands on windows may only be killed using the /F options which probably is like SIGKILL. This is bad as the process might be doing something, leaving the resource locked and/or in an inconsistent state. Without the /F option, git does not terminate itself, probably it listens to SIGINT which is not sent by TASKKILL.
We can't really help it, but may be at some point git handles windows signals properly.
See whether its git that doesn't do it right, or whether there is a way to send different signals on windows that git will understand.
The text was updated successfully, but these errors were encountered:
git commands on windows may only be killed using the /F options which probably is like SIGKILL. This is bad as the process might be doing something, leaving the resource locked and/or in an inconsistent state. Without the /F option, git does not terminate itself, probably it listens to SIGINT which is not sent by TASKKILL.
We can't really help it, but may be at some point git handles windows signals properly.
See whether its git that doesn't do it right, or whether there is a way to send different signals on windows that git will understand.
The text was updated successfully, but these errors were encountered: