Re: Question about the revision walking API

Mike Hommey m...@glandium.org writes: I would like to know if the revision walking API works as one would expect with a calling sequence like the following: - init_revisions - add_pending_object/setup_revisions - prepare_revision_walk - get_revision (repeated) - reset_revision_walk (I

Re: Question about the revision walking API

On Tue, Jan 06, 2015 at 02:24:58AM -0800, Junio C Hamano wrote: Mike Hommey m...@glandium.org writes: I would like to know if the revision walking API works as one would expect with a calling sequence like the following: - init_revisions - add_pending_object/setup_revisions -

Re: Question about the revision walking API

Hi, On Tue, Jan 6, 2015 at 3:02 AM, Mike Hommey m...@glandium.org wrote: Hi, I would like to know if the revision walking API works as one would expect with a calling sequence like the following: - init_revisions - add_pending_object/setup_revisions - prepare_revision_walk -

Re: Question about the revision walking API

Christian Couder christian.cou...@gmail.com writes: I am not sure what you describe above would work, but something like what is done in bisect.c should work, see check_ancestors() and bisect_next_all(). It might not be the most efficient solution though, so I am interested if you find

Question about the revision walking API

Hi, I would like to know if the revision walking API works as one would expect with a calling sequence like the following: - init_revisions - add_pending_object/setup_revisions - prepare_revision_walk - get_revision (repeated) - reset_revision_walk (I guess) - add_pending_object -