• Mike Bierlee (5/5) Mar 18 2017 According to github, issue 17057 was merged into master last
• Sebastian Wilzbach via Dlang-internal (9/14) Mar 19 2017 For reference the regarding commit:

Mike Bierlee <m.bierlee lostmoment.com> writes:

According to github, issue 17057 was merged into master last 
January but doesn't seem to be in any of the following releases. 
I cannot find it in any of the changelogs. When running the test 
on DMD32 on Windows, the bug is still there.
What happened to the merge?

Sebastian Wilzbach via Dlang-internal <dlang-internal puremagic.com> writes:

For reference the regarding commit:

https://github.com/dlang/dmd/commit/6280bb4437c05f418e852dad65c7f09ae2b43dd7

2.073.0 was released on 2017-01-22. The patch releases contain only bug fixes
targeted at stable. 
So yeah, this PR should have targeted stable. As this tends to get forgotten
quite frequently I wrote a PR some time ago: 
https://github.com/dlang-bots/dlang-bot/pull/57

Btw please note that the merge window usually closes one or two weeks before a
new minor release and that 2.074 is right around the corner:

http://dlang.org/changelog/2.074.0_pre.html

Last but not least Git(Hub) allows to show all tags which contain a commit
which is an empty set for the commit in question. 

On March 18, 2017 11:55:19 AM GMT+01:00, Mike Bierlee via Dlang-internal
<dlang-internal puremagic.com> wrote:
According to github, issue 17057 was merged into master last 
January but doesn't seem to be in any of the following releases. 
I cannot find it in any of the changelogs. When running the test 
on DMD32 on Windows, the bug is still there.
What happened to the merge?