git-commit.sh: Fix usage checks regarding paths given when they do not make sense
authorBjörn Steinbrink <B.Steinbrink@gmx.de>
Mon, 5 Nov 2007 19:36:33 +0000 (20:36 +0100)
committerJunio C Hamano <gitster@pobox.com>
Tue, 6 Nov 2007 05:36:31 +0000 (21:36 -0800)
commit34cb704a9b8b45ff3e1342678c5892e1ee6e27f5
treeeabac2fbc639592cc1f3c4307407fc658f3415f6
parentd8e21ba8967f43b61fc2fd50dd749ff8f0c6592a
git-commit.sh: Fix usage checks regarding paths given when they do not make sense

The checks that looked for paths given to git-commit in addition to
--all or --interactive expected only 3 values, while the case statement
actually provides 4, so the check was never triggered.

The bug was introduced in 6cbf07efc5702351897dee4742525c9b9f7828ac when
the case statement was extended to handle --interactive.

Signed-off-by: Björn Steinbrink <B.Steinbrink@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
git-commit.sh