"Michael S. Tsirkin" [off-list ref] writes:
Quoting Michael S. Tsirkin [off-list ref]:
quoted
quoted
Because I *got* *rid* *of* "echo".
so I think we are stuck with echo.
So ... is it good to go?
I am not quite convinced that giving a short summary is
necessary yet, probably for the same reason you questioned why
we do --shortstat.
Junio C Hamano [off-list ref] wrote:
"Michael S. Tsirkin" [off-list ref] writes:
quoted
Quoting Michael S. Tsirkin [off-list ref]:
quoted
quoted
Because I *got* *rid* *of* "echo".
so I think we are stuck with echo.
So ... is it good to go?
I am not quite convinced that giving a short summary is
necessary yet, probably for the same reason you questioned why
we do --shortstat.
Its not really necessary, no.
But when you have 8 terminal windows open, and you haven't looked
at one in a while, and it has a nice output from current git-reset
showing the subject of the commit you just reset to, that's handy
to jog your memory about what the shell was doing before it got
shuffled off the desk.
Now look at a git-commit output and find that's missing. If its
cheap (and it is, reasonably so) it may be useful to some people.
Of course I'm one of those "gah, I got more shells than I know what
I'm doing with!" people. ;-)
--
Shawn.
On 4/16/07, Shawn O. Pearce [off-list ref] wrote:
quoted
I am not quite convinced that giving a short summary is
necessary yet, probably for the same reason you questioned why
we do --shortstat.
Of course I'm one of those "gah, I got more shells than I know what
I'm doing with!" people. ;-)
Me too. Please, can we have it? :)