| commit | f3f056a396bbcdcd05ba23b425b0c93602976b0d | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Wed, 26 Mar 2008 06:45:47 +0000 (25 23:45 -0700) | ||
| committer | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Sun, 7 Feb 2010 19:17:11 +0000 (7 20:17 +0100) | ||
| tree | 7af02be81965786d76fdb1791d2971a203dd07c0 | treesnapshot (tar.gz zip) |
| parent | 5d821843a21a88ac0f22c909025127ee37dc45ca | commitdiff |
fsck --lost-found: show found commits human readably
An earlier commit fc8b5f0 (Deprecate git-lost-found, 2007-11-08) declared
"lost-found" deprecated, because "fsck" learned "--lost-found" option that
drops the found objects in $GIT_DIR/lost-found.
But the output from the lost-found program has been much more informative
than the plain vanilla "git fsck" (or "git fsck --lost-found") output. In
that sense, forcing users to use "fsck --lost-found" when they want to use
"lost-found" is a regression.
This patch slightly enhances the output from "fsck --lost-found" to add
oneline description at the end of the usual "dangling <type> <sha-1>"
message for commit objects it found.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
An earlier commit fc8b5f0 (Deprecate git-lost-found, 2007-11-08) declared
"lost-found" deprecated, because "fsck" learned "--lost-found" option that
drops the found objects in $GIT_DIR/lost-found.
But the output from the lost-found program has been much more informative
than the plain vanilla "git fsck" (or "git fsck --lost-found") output. In
that sense, forcing users to use "fsck --lost-found" when they want to use
"lost-found" is a regression.
This patch slightly enhances the output from "fsck --lost-found" to add
oneline description at the end of the usual "dangling <type> <sha-1>"
message for commit objects it found.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin-fsck.c | diffblobblamehistory |