Oh, I was wrong about 'git bisect' actually allowing --first parent (it was
just an expectation ;-),
Though it should, based on a quick search for 'git bisect --first-parent'
which gives quite a few mini-scripts to create the appropriate 'good'
<boundary> commit list to see where the defect was merged in.
Philip
----- Original Message -----
From: "Philip Oakley" <philipoak...@iee.org>
Hi Marc,
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 started at
https://public-inbox.org/git/1397681938-18594-1-git-send-email-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 bisect
On Tue, Dec 26, 2017 at 05:54:21PM -0000, 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 will trim the search
history.
Is there a best practice about how to choose those history points?
> IIRC you can also use the parsing options such as --first-parent to
limit
> the search history (so you find the point that the bad issue was merged
in).
Which git subcommand has this --first-parent option, and what would be
my benefit of using it?
> One thing to do is to use 'git describe' for the good tag/commit and
> the
> commit found by the bisect and look at the implied history of the
> ^I~J^K~L^M~N history flows, I guess that you will find that the
> bisected
> commit is from such a side branch.
You totally lost me here. Can you explain please?
Greetings
Marc, using git on a daily basis for years but still obviously well
within the first third of the learning curve
--
You received this message because you are subscribed to the Google Groups "Git for
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
