diff options
| author | Jeff King <peff@peff.net> | 2015-06-01 05:56:37 -0400 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2015-06-01 09:29:50 -0700 |
| commit | daf7d86783b1bd2065881a3f0957f69c79a52fd7 (patch) | |
| tree | 9b267ef958474b6bef66806bab3963cc4b7e6073 /list-objects.c | |
| parent | 9cc2b07a7c95fad0bb5e3a7a8db29bebdb90d92b (diff) | |
| download | git-daf7d86783b1bd2065881a3f0957f69c79a52fd7.tar.gz | |
silence broken link warnings with revs->ignore_missing_links
We set revs->ignore_missing_links to instruct the
revision-walking machinery that we know the history graph
may be incomplete. For example, we use it when walking
unreachable but recent objects; we want to add what we can,
but it's OK if the history is incomplete.
However, we still print error messages for the missing
objects, which can be confusing. This is not an error, but
just a normal situation when transitioning from a repository
last pruned by an older git (which can leave broken segments
of history) to a more recent one (where we try to preserve
whole reachable segments).
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'list-objects.c')
| -rw-r--r-- | list-objects.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/list-objects.c b/list-objects.c index 2910becd6c..90c21abc5c 100644 --- a/list-objects.c +++ b/list-objects.c @@ -81,7 +81,7 @@ static void process_tree(struct rev_info *revs, die("bad tree object"); if (obj->flags & (UNINTERESTING | SEEN)) return; - if (parse_tree(tree) < 0) { + if (parse_tree_gently(tree, revs->ignore_missing_links) < 0) { if (revs->ignore_missing_links) return; die("bad tree object %s", sha1_to_hex(obj->sha1)); |