Author Topic: Nightly (Windows): 11 May 2015 - Revision 1fe476a  (Read 1193 times)

0 Members and 1 Guest are viewing this topic.

Offline SirKnightly

  • George or Keira?
  • 212
Nightly (Windows): 11 May 2015 - Revision 1fe476a
Here is the nightly for Windows on 11 May 2015 - Revision 1fe476a

Open non-feature issues in Mantis: 123

Group: Standard
fso_Standard_20150511_1fe476a.7z
MD5Sum

Group: NO-SSE
fso_NO-SSE_20150511_1fe476a.7z
MD5Sum

Group: AVX
fso_AVX_20150511_1fe476a.7z
MD5Sum

Group: SSE
fso_SSE_20150511_1fe476a.7z
MD5Sum

Code: [Select]
------------------------------------------------------------------------
commit aa6936a
Author: asarium <Thu May 7 18:27:48 2015 +0200>
Commit: asarium <Thu May 7 18:27:48 2015 +0200>

    From LotF: Fix for Mantis 3134
 code/io/keycontrol.cpp | 128 +++++++++++++++++++++++++++++++------------------
 1 file changed, 82 insertions(+), 46 deletions(-)



 

Offline Luis Dias

  • 211
Re: Nightly (Windows): 11 May 2015 - Revision 1fe476a
Oh... I miss the decimal revision number. How do these git revision numbers work anyway?

 

Offline The E

  • He's Ebeneezer Goode
  • Moderator
  • 213
  • Nothing personal, just tech support.
    • Steam
    • Twitter
Re: Nightly (Windows): 11 May 2015 - Revision 1fe476a
Git assigns SHA-1 hashes to each revision.
If I'm just aching this can't go on
I came from chasing dreams to feel alone
There must be changes, miss to feel strong
I really need lifе to touch me
--Evergrey, Where August Mourns

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: Nightly (Windows): 11 May 2015 - Revision 1fe476a
For a quick way to tell which revision is newer than which, just look at the date (these nightlies use that as their "revision number" so it'll show up in debug logs and suchlike, e.g. "3.7.3.20150511").
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.