Thread (16 messages) flat view 16 messages, 9 authors, 2016-08-11

Re: [PATCH 0/2] Making "git commit" to mean "git commit -a".

From: Josef Weidendorfer <hidden>
Date: 2016-08-11 20:04:44

Possibly related (same subject, not in this thread)

On Tuesday 28 November 2006 07:59, Junio C Hamano wrote:
Once I am done, I can ask "git diff" and expect it to show my
local changes I have no intention of committing for now
...

And at that point, I trust "git commit" to do the right thing --
the damn thing I just checked with "git diff --cached" _is_ what
will be committed.
I think the difference behavior between "git commit" and "git diff" is
a little bit confusing.

Currently, we have
* "git diff" shows what "git commit -a" would commit
* "git diff --cached" shows what "git commit" would commit

IMHO, "git diff" should show what's in the staging area,
and we should introduce "git diff -a" as a way to see the full
changes.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help