diff options
| author | Michael Haggerty <mhagger@alum.mit.edu> | 2017-09-13 20:15:55 +0300 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2017-09-14 09:19:07 +0300 |
| commit | 8738a8a4df9ee50112b5f5a757c58988166974d3 (patch) | |
| tree | 2c7b060f1d6f7a7f0c6684c1e59e1adff9395433 /refs/ref-cache.c | |
| parent | 5e00a6c873981f87165adfecf29ad0ecc2c2c5df (diff) | |
ref_iterator: keep track of whether the iterator output is ordered
References are iterated over in order by refname, but reflogs are not.
Some consumers of reference iteration care about the difference. Teach
each `ref_iterator` to keep track of whether its output is ordered.
`overlay_ref_iterator` is one of the picky consumers. Add a sanity
check in `overlay_ref_iterator_begin()` to verify that its inputs are
ordered.
Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'refs/ref-cache.c')
| -rw-r--r-- | refs/ref-cache.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/refs/ref-cache.c b/refs/ref-cache.c index 76bb723c86..54dfb5218c 100644 --- a/refs/ref-cache.c +++ b/refs/ref-cache.c @@ -574,7 +574,7 @@ struct ref_iterator *cache_ref_iterator_begin(struct ref_cache *cache, iter = xcalloc(1, sizeof(*iter)); ref_iterator = &iter->base; - base_ref_iterator_init(ref_iterator, &cache_ref_iterator_vtable); + base_ref_iterator_init(ref_iterator, &cache_ref_iterator_vtable, 1); ALLOC_GROW(iter->levels, 10, iter->levels_alloc); iter->levels_nr = 1; |