Public message to Hack

[Pir4nhaX]

Hi again fella, its been a while...
Im kinda working again to do some things with the Mupen 64 core.
My suggestion and i dont know what the ppl think about, is... do a small changelog on every version or change that you or anyone from the mupen 64 team touch. It only make things more clear and its easier to read the changes that try to find all the new code in the source.

Take care, and lemme see what i can do....

PS: Im gonna go again to the channel, its been 2 years almost.

EDIT: Actually, its gonna be 3 years :)

[juwb]

Well, you can always use diff :happy:, or use CVS / SVN for versioning. It has a lot of benefits, especially if you work in a team... it can show you exactly who changed which lines of code and why.

[Pir4nhaX]

Well, you can always use diff :happy:, or use CVS / SVN for versioning. It has a lot of benefits, especially if you work in a team... it can show you exactly who changed which lines of code and why.

All i ask is a changelog... i have the latest source (probably 1 that you cant get), but anyhow, since i stop working with Mupen64, i dont remember whats new... i totally stoped the project, and im getting in again.
Anyway, thanks for your answer.