Michael Haggerty 8738a8a4df 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>		2017-09-14 15:19:07 +09:00
..
files-backend.c	ref_iterator: keep track of whether the iterator output is ordered	2017-09-14 15:19:07 +09:00
iterator.c	ref_iterator: keep track of whether the iterator output is ordered	2017-09-14 15:19:07 +09:00
packed-backend.c	ref_iterator: keep track of whether the iterator output is ordered	2017-09-14 15:19:07 +09:00
packed-backend.h	packed-backend: rip out some now-unused code	2017-09-09 03:18:04 +09:00
ref-cache.c	ref_iterator: keep track of whether the iterator output is ordered	2017-09-14 15:19:07 +09:00
ref-cache.h	ref_iterator: keep track of whether the iterator output is ordered	2017-09-14 15:19:07 +09:00
refs-internal.h	ref_iterator: keep track of whether the iterator output is ordered	2017-09-14 15:19:07 +09:00