Teach revision walking machinery to walk multiple times sequencially
Previously it was not possible to iterate revisions twice using the revision walking api. We add a reset_revision_walk() which clears the used flags. This allows us to do multiple sequencial revision walks. We add the appropriate calls to the existing submodule machinery doing revision walks. This is done to avoid surprises if future code wants to call these functions more than once during the processes lifetime. Signed-off-by: Heiko Voigt <hvoigt@hvoigt.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:

committed by
Junio C Hamano

parent
6f5e880c68
commit
bcc0a3ea38
@ -404,6 +404,7 @@ int check_submodule_needs_pushing(unsigned char new_sha1[20], const char *remote
|
||||
while ((commit = get_revision(&rev)) && !needs_pushing)
|
||||
commit_need_pushing(commit, &needs_pushing);
|
||||
|
||||
reset_revision_walk();
|
||||
free(sha1_copy);
|
||||
strbuf_release(&remotes_arg);
|
||||
|
||||
@ -741,6 +742,7 @@ static int find_first_merges(struct object_array *result, const char *path,
|
||||
if (in_merge_bases(b, &commit, 1))
|
||||
add_object_array(o, NULL, &merges);
|
||||
}
|
||||
reset_revision_walk();
|
||||
|
||||
/* Now we've got all merges that contain a and b. Prune all
|
||||
* merges that contain another found merge and save them in
|
||||
|
Reference in New Issue
Block a user