| commit | 89bc8c785e20258efba3b2b5ffc26098fa0b8bc8 | |
| author | Amos Waterland <apw@rossby.metr.ou.edu> | |
| Thu, 1 Sep 2005 14:13:50 +0000 (1 09:13 -0500) | ||
| committer | Junio C Hamano <junkio@cox.net> | |
| Fri, 2 Sep 2005 04:45:00 +0000 (1 21:45 -0700) | ||
| tree | 3260ded767eb47cfa959cdc46d35ef9e4b6d1a16 | treesnapshot (tar.gz zip) |
| parent | a1d4aa742416953a3ac9be9154c55e90a4193cd6 | commitdiff |
[PATCH] Explain what went wrong on update-cache of new file
If somebody tries to run `git update-cache foo', where foo is a new
file, git dies with a rather cryptic error message:
fatal: Unable to add foo to database
This trivial patch makes git explain what probably went wrong. It is
not a perfect diagnosis of all error paths, but for 90% of the cases it
should provide the user with the clue they need.
[jc: I ended up wording slightly differently, and fixed another
confusing error message I noticed while reviewing the code.]
Signed-off-by: Amos Waterland <apw@rossby.metr.ou.edu>
Signed-off-by: Junio C Hamano <junkio@cox.net>
If somebody tries to run `git update-cache foo', where foo is a new
file, git dies with a rather cryptic error message:
fatal: Unable to add foo to database
This trivial patch makes git explain what probably went wrong. It is
not a perfect diagnosis of all error paths, but for 90% of the cases it
should provide the user with the clue they need.
[jc: I ended up wording slightly differently, and fixed another
confusing error message I noticed while reviewing the code.]
Signed-off-by: Amos Waterland <apw@rossby.metr.ou.edu>
Signed-off-by: Junio C Hamano <junkio@cox.net>
| update-cache.c | diffblobblamehistory |