On Sunday 13 July 2008 17:40:03 Johannes Schindelin wrote:
> No, last time I checked I could kill a long-running git-rev-list with
> "kill" just fine. Something else must be wrong.
>
> Please investigate,
OK, so I run 'git gui blame SomeFile' in one window, and look at the list
of processes from another one. Here it is, with irrelevant parts removed:
$ ps -W
PID PPID PGID WINPID TTY UID STIME COMMAND
904 1 904 904 con 500 14:38:44 /bin/bash
1008 904 1008 1008 con 500 18:11:20 /bin/git
(bash.exe)
976 0 0 976 ? 0 18:11:20 c:\msysgit\bin\git.exe
344 1 344 344 con 500 18:11:20 /mingw/bin/wish
(sh.exe)
1104 0 0 1104 ? 0 18:11:20
c:\msysgit\mingw\bin\wish.exe
736 0 0 736 ? 0 18:11:45
C:\msysgit\bin\git-blame.exe
(In parentheses I specified what Task Manager thinks about the process)
I can kill 1008 and 344, and it cascades to 976 and 1104 respectively.
But 736 continues running and hogging the CPU, and when I try to kill it, I get:
$ kill 736
bash: kill: (736) - No such process
> P.S.: Use Git Bash only is the default, because most of the contributors
> to msysGit prefer that option (Hannes being the notable exception). Once
> most contributors prefer another option, we will switch.
Ok, I'll just build my own installer if it becomes a problem =)
> P.P.S.: Why do you ask a different question in a P.S., risking it to be
> missed?
It seemed too trivial for a separate message.
> P.P.P.S.: Why do you put the verb in the question after the subject
> instead of before it? :-)
Editing artifact, I suppose =)
Alexander
