| commit | fa39b6b5b11f9b580c515a7b4a8e4eb8eaa79b75 | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Fri, 22 Dec 2006 00:48:32 +0000 (21 19:48 -0500) | ||
| committer | Junio C Hamano <junkio@cox.net> | |
| Fri, 22 Dec 2006 06:59:34 +0000 (21 22:59 -0800) | ||
| tree | 1b01d4e00ef4367a922de3f7a0e553bff2266073 | treesnapshot (tar.gz zip) |
| parent | 51dcaa9686d9ff591e9d051e6090d8529bc263a5 | commitdiff |
Introduce a global level warn() function.
Like the existing error() function the new warn() function can be
used to describe a situation that probably should not be occuring,
but which the user (and Git) can continue to work around without
running into too many problems.
An example situation is a bad commit SHA1 found in a reflog.
Attempting to read this record out of the reflog isn't really an
error as we have skipped over it in the past.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Like the existing error() function the new warn() function can be
used to describe a situation that probably should not be occuring,
but which the user (and Git) can continue to work around without
running into too many problems.
An example situation is a bad commit SHA1 found in a reflog.
Attempting to read this record out of the reflog isn't really an
error as we have skipped over it in the past.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
| git-compat-util.h | diffblobblamehistory | |
| usage.c | diffblobblamehistory |