summaryrefslogtreecommitdiff
path: root/t/t5580-clone-push-unc.sh
diff options
context:
space:
mode:
authorLibravatar Johannes Schindelin <johannes.schindelin@gmx.de>2016-07-17 12:59:49 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-07-18 11:35:00 -0700
commit7b35efd734e501f9e4692768a8b6aea818c0c93e (patch)
tree305cc01660799f6b73d1ede6360b03046077bccc /t/t5580-clone-push-unc.sh
parentfsck: refactor how to describe objects (diff)
downloadtgif-7b35efd734e501f9e4692768a8b6aea818c0c93e.tar.xz
fsck_walk(): optionally name objects on the go
If fsck_options->name_objects is initialized, and if it already has name(s) for the object(s) that are to be the starting point(s) for fsck_walk(), then that function will now add names for the objects that were walked. This will be highly useful for teaching git-fsck to identify root causes for broken links, which is the task for the next patch in this series. Note that this patch opts for decorating the objects with plain strings instead of full-blown structs (à la `struct rev_name` in the code of the `git name-rev` command), for several reasons: - the code is much simpler than if it had to work with structs that describe arbitrarily long names such as "master~14^2~5:builtin/am.c", - the string processing is actually quite light-weight compared to the rest of fsck's operation, - the caller of fsck_walk() is expected to provide names for the starting points, and using plain and simple strings is just the easiest way to do that. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5580-clone-push-unc.sh')
0 files changed, 0 insertions, 0 deletions