Re: [PATCH v2 3/6] bisect: use refs infrastructure for BISECT_START
- From
David Turner <dturner@twopensource.com>
- Date
- Jun 26, 2015, 00:22 UTC
- Message-ID
- <1435278173.7900.27.camel@twopensource.com>
- In-Reply-To
- <1435274490.7900.19.camel@twopensource.com>
On Thu, 2015-06-25 at 19:21 -0400, David Turner wrote:
Show 11 quoted lines
> On Thu, 2015-06-25 at 13:52 -0700, Junio C Hamano wrote: > > David Turner <dturner@twopensource.com> writes: > > > > > This ref needs to go through the refs backend, since some code assumes > > > that it can be written and read as a ref. > > > > And the reason why BISECT_HEAD cannot be treated as a ref, but must > > be treated as a file under $GIT_DIR, is...? > > After running some tests on the long version of the series, we can and > should move it into the backend; will add a patch to the next reroll
Actually, I've looked into this further. BISECT_START isn't a ref because it contains the ref name that the bisection started from (not a symbolic ref). BISECT_HEAD is a ref. Will fix.