Should we 'rebase.exe' msys-1.0.dll again?
Johannes Schindelin
I just realized that upstream msys-1.0.dll is rebased to 0x71000000, while
we rebase to 0x30000000. Should we adjust that?
I am hesitant, as I want to release Git for Windows 1.6.4 Real Soon Now
(so that we can claim to be better than Subversion because we have a
higher version number, nyanyanyaaah!).
Opinions?
Ciao,
Dscho
Peter Harris
The msys dll we ship is modified from the upstream version in other
respects already, right? I don't see any reason to keep our base in
sync with their base.
In my opinion, the important thing is that all our images have
different bases so they don't get auto-rebased by the OS at run-time
(which leads to fork emulation failures).
Peter Harris
Johannes Schindelin
The problem is that I saw a report (in #git on IRC of all places) that our
msys-1.0.dll does not work on a certain Vista (64-bit) installation.
Of course, that guy said "yes, yes" when I asked to report the issue
_here_, and of course -- as the Windows users I grew to hate so much over
the time working on msysGit -- he did not do that. I do not even know if
he found a solution.
I tell you, this behavior sucks royally. I certainly do not deserve that.
In any case, my idea was that maybe MSys chose a sensible address range
after a careful analysis what might clash least with any existing
software.
But that is too late for 1.6.4 now, and that serves that guy right.
Ciao,
Dscho