On Tue, Dec 26, 2017 at 05:54:21PM -, Philip Oakley wrote:
> Each time you give a 'good' history point it will trim the search history.
And adding "bad" history points will increase it, right? Marking
4.13-rc5, -rc6 and -rc7 as "bad" has increased the number of steps, and
adding "good" points
Hi Philip,
On Wed, Dec 27, 2017 at 04:58:16PM -, Philip Oakley wrote:
> Found the reference article about 'git describe' and the way commits can
> 'bypass' (or appear to) the expected tags.
>
> https://public-inbox.org/git/20140422040443.gc9...@odin.tremily.us/ shows the
> discussion which
03
To: git-users@googlegroups.com
Subject: Re: [git-users] need explanation re git bisect
On Tue, Dec 26, 2017 at 05:54:21PM -, Philip Oakley wrote:
> The key points were that bisect will search *all* heirarchy paths
(unless
> you tell it different). This means that all side heirarchies are als
-mcg...@do-not-panic.com/
Philip
> -Original Message-
> From: git-users@googlegroups.com [mailto:git-users@googlegroups.com] On
> Behalf Of Marc Haber
> Sent: 27 December 2017 12:03
> To: git-users@googlegroups.com
> Subject: Re: [git-users] need explanation re git bisec
On Tue, Dec 26, 2017 at 05:54:21PM -, Philip Oakley wrote:
> The key points were that bisect will search *all* heirarchy paths (unless
> you tell it different). This means that all side heirarchies are also places
> that bisect will search.
>
> Each time you give a 'good' history point it
Hi Mark,
quick comment.
Possibly include more good commits in the list. I suspect that there are
multiple branches that merge into master between those two tags, and that
some of those brancfes have fork points from before the given good tag, so
git has to search down all of those other side
