author | Junio C Hamano <junkio@cox.net> | |
Thu, 8 Mar 2007 10:12:06 +0000 (02:12 -0800) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Wed, 14 Mar 2007 08:33:41 +0000 (01:33 -0700) | ||
commit | 0497c620cae0531815afc4ada783b488eab3f447 | |
tree | de01b8eed6e9994651491c7452445a605255585e | tree | snapshot |
parent | 86952cdabdcc550a20794794db539c41877d17fc | commit | diff |
shortlog: prompt when reading from terminal by mistake
I was trying to see who have been active recently to find GSoC
mentor candidates by running:
$ git shortlog -s -n --since=4.months | head -n 20
After waiting for about 20 seconds, I started getting worried,
thinking that the recent revision traversal updates might have
had an unintended side effect.
Not so. "git shortlog" acts as a filter when no revs are given,
unlike "git log" which defaults to HEAD. It was reading from
its standard input.
Signed-off-by: Junio C Hamano <junkio@cox.net>
I was trying to see who have been active recently to find GSoC
mentor candidates by running:
$ git shortlog -s -n --since=4.months | head -n 20
After waiting for about 20 seconds, I started getting worried,
thinking that the recent revision traversal updates might have
had an unintended side effect.
Not so. "git shortlog" acts as a filter when no revs are given,
unlike "git log" which defaults to HEAD. It was reading from
its standard input.
Signed-off-by: Junio C Hamano <junkio@cox.net>
builtin-shortlog.c | diff | blob | history |