[PATCH 6/7] revision cache: allow foreign 'start' commits
- From
Sam Vilain <sam@vilain.net>
- Date
- Jun 4, 2009, 14:05 UTC
- Message-ID
- <14c3b1136cea650af9a3274b260c0a708456a554.1244125128.git.sam@vilain.net>
- In-Reply-To
- <cover.1244125127.git.sam@vilain.net>
Usually the 'start' commits are always 'interesting' commits in a revision query, however with the 'newness' bitmaps we can also use them to mask out objects, ie 'uninteresting' commits. An index which was useless, due to an unknown object existing in the 'uninteresting' commit list can be converted to a useful one by building the bitmap of 'reachable' and 'new' objects for that commit - without having to insert new objects in the middle of the list, which would require rebuilding the entire index. So, there is a use case for storing information on 'start' objects which aren't actually in the object list. Permit this case.
This is currently a work in progress; extension to how this affects the use cases is not there yet.
Signed-off-by: Sam Vilain <sam@vilain.net> --- Documentation/technical/revision-cache.txt | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/Documentation/technical/revision-cache.txt b/Documentation/technical/revision-cache.txt index e0adb26..0cd7b08 100644 --- a/Documentation/technical/revision-cache.txt +++ b/Documentation/technical/revision-cache.txt @@ -33,6 +33,10 @@ A revision cache contains; 'end' object, but not reachable from the 'start' objects reachable from that 'end' object. + - a list of 'foreign end' objects, for which not all reachable + objects are in the object list, but can have reachability or a + 'newness' bitmap. + Start Objects and End Objects -----------------------------
-- debian.1.5.6.1