git/refs at 5b633610ec7a6c10f55e4758b047892652da8e05 - git

Tree: 5b633610ec

Michael Haggerty 5b633610ec packed_ref_cache: keep the `packed-refs` file mmapped if possible Keep a copy of the `packed-refs` file contents in memory for as long as a `packed_ref_cache` object is in use: * If the system allows it, keep the `packed-refs` file mmapped. * If not (either because the system doesn't support `mmap()` at all, or because a file that is currently mmapped cannot be replaced via `rename()`), then make a copy of the file's contents in heap-allocated space, and keep that around instead. We base the choice of behavior on a new build-time switch, `MMAP_PREVENTS_DELETE`. By default, this switch is set for Windows variants. After this commit, `MMAP_NONE` and `MMAP_TEMPORARY` are still handled identically. But the next commit will introduce a difference. This whole change is still pointless, because we only read the `packed-refs` file contents immediately after instantiating the `packed_ref_cache`. But that will soon change. Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu> Signed-off-by: Junio C Hamano <gitster@pobox.com>		8 years ago
..
files-backend.c	ref_iterator: keep track of whether the iterator output is ordered	8 years ago
iterator.c	prefix_ref_iterator: break when we leave the prefix	8 years ago
packed-backend.c	packed_ref_cache: keep the `packed-refs` file mmapped if possible	8 years ago
packed-backend.h	packed-backend: rip out some now-unused code	8 years ago
ref-cache.c	ref_iterator: keep track of whether the iterator output is ordered	8 years ago
ref-cache.h	ref_iterator: keep track of whether the iterator output is ordered	8 years ago
refs-internal.h	ref_iterator: keep track of whether the iterator output is ordered	8 years ago