summaryrefslogtreecommitdiff
path: root/contrib/persistent-https/README
diff options
context:
space:
mode:
authorLibravatar Johannes Schindelin <johannes.schindelin@gmx.de>2016-07-17 13:00:02 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-07-18 15:15:59 -0700
commit90cf590f53f2939a47ca7b397e270e8228699829 (patch)
tree54a32ad0aa0098c039f7a5a12ac9ca8e3a4febde /contrib/persistent-https/README
parentfsck: give the error function a chance to see the fsck_options (diff)
downloadtgif-90cf590f53f2939a47ca7b397e270e8228699829.tar.xz
fsck: optionally show more helpful info for broken links
When reporting broken links between commits/trees/blobs, it would be quite helpful at times if the user would be told how the object is supposed to be reachable. With the new --name-objects option, git-fsck will try to do exactly that: name the objects in a way that shows how they are reachable. For example, when some reflog got corrupted and a blob is missing that should not be, the user might want to remove the corresponding reflog entry. This option helps them find that entry: `git fsck` will now report something like this: broken link from tree b5eb6ff... (refs/stash@{<date>}~37:) to blob ec5cf80... Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'contrib/persistent-https/README')
0 files changed, 0 insertions, 0 deletions