Re: [PATCH v2 6/6] revision.c: refactor basic topo-order logic

On Tue, Sep 18 2018, Derrick Stolee via GitGitGadget wrote: > diff --git a/revision.h b/revision.h > index fd4154ff75..b20c16c0e0 100644 > --- a/revision.h > +++ b/revision.h > @@ -24,6 +24,8 @@ > #define USER_GIVEN (1u<<25) /* given directly by the user */ > #define TRACK_LINEAR (1u<<26) >

[PATCH v2 6/6] revision.c: refactor basic topo-order logic

From: Derrick Stolee When running a command like 'git rev-list --topo-order HEAD', Git performed the following steps: 1. Run limit_list(), which parses all reachable commits, adds them to a linked list, and distributes UNINTERESTING flags. If all unprocessed commits are UNINTERESTING, then