Page 1 of 1

Pre-2014 GitGub repository?

Posted: 2017-12-19, 23:13
by SpockFan02
I was looking in the MoonchildProductions/Pale-Moon commit log and found that it began in 2014: "Create new repo after line endings mishap." What happened, and where can I find older commits?

Re: Pre-2014 GitGub repository?

Posted: 2017-12-20, 03:59
by New Tobin Paradigm
That's it. there was no version control before that.. Old source code is up somewhere..

Re: Pre-2014 GitGub repository?

Posted: 2017-12-20, 05:35
by SpockFan02
Huh, okay. Do you know what the "line endings mishap" was? It sounds mysterious...

Also, where should I look for the 20.3 source code?

Re: Pre-2014 GitGub repository?

Posted: 2017-12-20, 08:38
by Moonchild
You can find old source code from the link on the source code web page.
The line endings mishap didn't mean anything beyond that -- when initially setting up the version control, the source tree was set to automatically have line endings converted between Windows and Unix-style (as is the default for git) but that's not good for our tree. So, shortly after the initial commit it was erased and re-done with the correct settings.

Re: Pre-2014 GitGub repository?

Posted: 2017-12-20, 12:13
by ketmar
Off-topic:
just built Pale Moon 3.6.32 for GNU/Linux (gcc 6.3.0). after some cosmetic source code fixes, it builds and works!
screenshot

Re: Pre-2014 GitGub repository?

Posted: 2017-12-20, 13:34
by New Tobin Paradigm
Hardcore!

Now backport css3, es5 and 6, and html5... Also, WHY? :P

Re: Pre-2014 GitGub repository?

Posted: 2017-12-20, 13:42
by ketmar
>Also, WHY?
kick me if i know! ;-) i just thought: "hey, it will be fun to try to build that. let's see how it will break!" and... it won't. sure, i had to do some cosmetic fixes (like changing `*_METHODIMP` to `*_METHOD` in class definitions, do "chmod +x" on some scripts, and so on), turn off modern misoptimisations ("-fno-strict-aliasing -fno-strict-overflow -fno-delete-null-pointer-checks -fwrapv"), and there are TONS of warnings, but otherwise -- it works!

also, it already supports HTML5 (as it was in 2012).