Re: [PATCH v2 5/9] bisect: avoid using the rev_info flag leak_pending
- From
Jeff King <peff@peff.net>
- Date
- Jan 12, 2018, 15:23 UTC
- Message-ID
- <20180112152353.GB10210@sigill.intra.peff.net>
- In-Reply-To
- <b0fbedea-77d8-5571-6042-03b512c0680d@web.de>
On Thu, Jan 11, 2018 at 07:57:51PM +0100, René Scharfe wrote:
Show 12 quoted lines
> > If we already have the list of tips, could we just feed it ourselves to > > bisect_rev_setup (I think that would require us remembering which were > > "good" and "bad", but that doesn't seem like a big deal). > > That's done already under the covers. De-globalizing these variables > would make this visible. > > Another way would be to store the bad and good revs in a format that > allows them to be used everywhere, thus avoiding confusing > duplication/conversions. Commit pointers and arrays thereof should > work everywhere we currently use object_ids and oid_arrays for bad > and good revs, right?
I think bisect_rev_setup() has to munge that into "^" and non-"^" arguments. Though arguably we could shove stuff into the pending commit list directly.
I dunno. It may not be worth spending more time on it.
-Peff