D Compiler Bug?

[H. S. Teoh]

On Tue, Feb 12, 2019 at 05:01:04PM +0000, Bottled Gin via Digitalmars-d wrote:
> On Tuesday, 12 February 2019 at 11:09:48 UTC, Petar Kirov [ZombineDev]
> wrote:
> > https://github.com/CyberShadow/Digger should help you do what you want.
> 
> Thanks.
> 
> Digger points me to a merge from another branch (which seems to have
> been deleted since), which actually pulls in about 400 PRs. It must be
> part of the release process.
> 
> Do I need to review all these 400 pull requests to figure out?

Shouldn't digger be able to narrow down those 400 PRs to something more
manageable?

There is no need to worry about branches being deleted; in git, branches
are merely references to commits. As long as you have the git repo, you
have all the information you need. All you have to do is to identify the
branch point of the branch (`git log --graph --oneline` is your friend)
and the tip of the branch, and digger should be able to bisect that
range to something more manageable.


T

-- 
Question authority. Don't ask why, just do it.