author | Johannes Schindelin <Johannes.Schindelin@gmx.de> | |
Sat, 20 May 2006 21:43:13 +0000 (23:43 +0200) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Sun, 21 May 2006 08:16:09 +0000 (01:16 -0700) | ||
commit | 8824689884a5673f803d77cda499f83b84145a06 | |
tree | 80b6437ce3928cf4e299c7ecd52d52e3e18a6eb5 | tree | snapshot |
parent | 845ae27bf8161063d7e2e1ca2a76b05bf5d07192 | commit | diff |
diff family: add --check option
Actually, it is a diff option now, so you can say
git diff --check
to ask if what you are about to commit is a good patch.
[jc: this also would work for fmt-patch, but the point is that
the check is done before making a commit. format-patch is run
from an already created commit, and that is too late to catch
whitespace damaged change.]
Signed-off-by: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Actually, it is a diff option now, so you can say
git diff --check
to ask if what you are about to commit is a good patch.
[jc: this also would work for fmt-patch, but the point is that
the check is done before making a commit. format-patch is run
from an already created commit, and that is too late to catch
whitespace damaged change.]
Signed-off-by: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Signed-off-by: Junio C Hamano <junkio@cox.net>
diff.c | diff | blob | history | |
diff.h | diff | blob | history |