3.1 release OSDN commit hash tag mismatch?
Posted: Fri Jan 21, 2022 12:19 am
When compiling the zandronum 3.1 server release "ZA_3.1 4178904d7698" tag from osdn
clients complain that...
Server uses: 3.1-R-300101-0000
You use: 3.1-R211211-2135
Is there a way or a proper commit hash I can use to access the proper source code for compiling a 3.1 release binary?
clients complain that...
Server uses: 3.1-R-300101-0000
You use: 3.1-R211211-2135
Is there a way or a proper commit hash I can use to access the proper source code for compiling a 3.1 release binary?