<div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Hi all,</div><div>In an obsolete working copy, I had some local changes to build.win32x86/thirdparty/Makefile.libssh2<br></div><div><span style="font-family:monospace,monospace"><br></span></div><div><div><span style="font-family:monospace,monospace">    tar x -f $(LIBSSH2ARCHIVE) -C $(THIRDPARTYDIR)<br>    cd $(LIBSSH2DIR) \<br>        && ./configure \<br>--            --build=x86_64-w64-cygwin \<br>++            --build=i686-w64-cygwin \<br>            --host=i686-w64-mingw32 \<br>            --prefix='$(THIRDPARTYOUTDIR)' \<br>            CFLAGS='$(THIRDPARTY_CFLAGS)' \</span><br></div><div><br></div><div>If I go into current version:</div><div><a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/build.linux32x86/third-party/Makefile.libssh2">https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/build.linux32x86/third-party/Makefile.libssh2</a></div><div><br></div><div>I don't see the x86_64 line, good, this must have been already fixed!</div><div>But when I look at history thru github interface to know when and how, I see a very partial and truncated history:</div><div><a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/commits/Cog/build.linux32x86/third-party/Makefile.libssh2">https://github.com/OpenSmalltalk/opensmalltalk-vm/commits/Cog/build.linux32x86/third-party/Makefile.libssh2</a></div><div><br></div><div>And itseems like none of the commits referenced did remove this x86_64 line, like if it never existed...<br></div><div><br></div><div>If I go a little further in the past commit log, in early november (still thru github interface <a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/commits/Cog?after=0fae80c28ee3ce2b3eb09cb31ec94f0a590893f7+174">https://github.com/OpenSmalltalk/opensmalltalk-vm/commits/Cog?after=0fae80c28ee3ce2b3eb09cb31ec94f0a590893f7+174</a>), select one of the commits and go tho this same file, then i see another unrelated short history:<br></div><div><a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/commits/fd213d14072e1099ded3590d99dd36e03562bcfe/build.win32x86/third-party/Makefile.libssh2">https://github.com/OpenSmalltalk/opensmalltalk-vm/commits/fd213d14072e1099ded3590d99dd36e03562bcfe/build.win32x86/third-party/Makefile.libssh2</a></div><div><br></div><div>This time, the x86_64 matching line is there...</div><div></div><div>This kind of unconventional rewrite of history makes me worry...</div><div>If we can't rely on history, then what a VCS is good for?</div><div><br></div><div>It's possible that the minheadless merge introduced that, so it would be good if more pairs of eyes could check that we did not loose anything important, especially for Pharo builds.</div><div><br></div></div></div></div></div>