summaryrefslogtreecommitdiff
path: root/revision.c
diff options
context:
space:
mode:
authorStefan Beller <sbeller@google.com>2017-11-16 02:00:35 (GMT)
committerJunio C Hamano <gitster@pobox.com>2017-11-16 02:12:51 (GMT)
commitce5b6f9be84690ba38eba10c42b3f7c7e2511abb (patch)
tree20994dc4791062d46a1d4418f7805503dd59a054 /revision.c
parent91904f5645196ceef92c6fca21cc9454928613f0 (diff)
downloadgit-ce5b6f9be84690ba38eba10c42b3f7c7e2511abb.zip
git-ce5b6f9be84690ba38eba10c42b3f7c7e2511abb.tar.gz
git-ce5b6f9be84690ba38eba10c42b3f7c7e2511abb.tar.bz2
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.c')
-rw-r--r--revision.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/revision.c b/revision.c
index d167223..9329d4e 100644
--- a/revision.c
+++ b/revision.c
@@ -1845,6 +1845,8 @@ static int handle_revision_opt(struct rev_info *revs, int argc, const char **arg
revs->dense = 0;
} else if (!strcmp(arg, "--show-all")) {
revs->show_all = 1;
+ } else if (!strcmp(arg, "--in-commit-order")) {
+ revs->tree_blobs_in_commit_order = 1;
} else if (!strcmp(arg, "--remove-empty")) {
revs->remove_empty_trees = 1;
} else if (!strcmp(arg, "--merges")) {