aboutsummaryrefslogtreecommitdiff
path: root/revision.h
diff options
context:
space:
mode:
authorStefan Beller <sbeller@google.com>2017-11-15 18:00:35 -0800
committerJunio C Hamano <gitster@pobox.com>2017-11-16 11:12:51 +0900
commitce5b6f9be84690ba38eba10c42b3f7c7e2511abb (patch)
tree20994dc4791062d46a1d4418f7805503dd59a054 /revision.h
parent91904f5645196ceef92c6fca21cc9454928613f0 (diff)
downloadgit-ce5b6f9be84690ba38eba10c42b3f7c7e2511abb.tar.gz
git-ce5b6f9be84690ba38eba10c42b3f7c7e2511abb.tar.xz
revision.h: introduce blob/tree walking in order of the commits
The functionality to list tree objects in the order they were seen while traversing the commits will be used in one of the next commits, where we teach `git describe` to describe not only commits, but blobs, too. The change in list-objects.c is rather minimal as we'll be re-using the infrastructure put in place of the revision walking machinery. For example one could expect that add_pending_tree is not called, but rather commit->tree is directly passed to the tree traversal function. This however requires a lot more code than just emptying the queue containing trees after each commit. Signed-off-by: Stefan Beller <sbeller@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'revision.h')
-rw-r--r--revision.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/revision.h b/revision.h
index 54761200a..86985d68a 100644
--- a/revision.h
+++ b/revision.h
@@ -121,7 +121,8 @@ struct rev_info {
bisect:1,
ancestry_path:1,
first_parent_only:1,
- line_level_traverse:1;
+ line_level_traverse:1,
+ tree_blobs_in_commit_order:1;
/* Diff flags */
unsigned int diff:1,