Closed lazka closed 2 months ago
I force-pushed after rebasing.
sure, looks good, thanks.
I'm confused why git rebase dropped that hunk.. there was no conflict.
double checked, and everything else is there at least.
I'm confused why git rebase dropped that hunk.. there was no conflict.
@lazka Aha! I looked a little bit more closely, and the original change to drop renaming CYGWIN_DEBUG
to MSYS_DEBUG
is in 38020a7e0e6a105b9d4bc25e745286014a36d17d, which is marked as a fixup!
of d1cb51f64425bb111e1f1cf002008642e1abf53f.
However, in that commit, the CYGWIN_DEBUG
variable was not renamed to MSYS_DEBUG
, at least not in winsup/cygwin/environ.cc
(but in winsup/cygwin/dcrt0.cc
). That was done two patches later, in ed83b2cc2e452756933227abe7a94cf6a5d5f49b.
So when the auto-squash tried to fix up the replayed d1cb51f64425bb111e1f1cf002008642e1abf53f by dropping that hunk, Git realized that the pre-image already had CYGWIN_DEBUG
and basically thought: hey, this is great, the change was already applied, good, nothing to be done, let's continue. But two patches later, that symbol was renamed to MSYS_DEBUG
and that's how we ended up here.
Oh, good catch. I kinda would have expected git to complain there somehow, either when doing the wrong fixup or when dropping it later. I need to be more careful next time.
changelog: https://cygwin.com/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/release/3.5.4
git range-diff cygwin-3.5.3..msys2-3.5.3 cygwin-3.5.4..wip/msys2-3.5.4
Actions taken: