Thread (29 messages) 29 messages, 8 authors, 2016-08-11

Re: [PATCH] make commit message a little more consistent and conforting

From: Junio C Hamano <hidden>
Date: 2016-08-11 19:22:47

Possibly related (same subject, not in this thread)

Nicolas Pitre [off-list ref] writes:
So in short I do think there should be something shown after a 
successful commit, and including the commit sha1 doesn't hurt.
...
And it is true that diffstat can be quite large.  I wouldn't mind the 
diffstat to be added to the commit message summary in the text editor 
though.  And displaying it when -v is used makes also a lot of sense.  
But not by default please.
I agree with everything you said in your message, including that
commit object name might help as a learning aid.

We could give something like this, though, if we wanted to:

	$ git commit
        4 files changed, 17 insertions(+), 10 deletions(-)
        mode change 100755 => 100644 test.sh
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help