kuteur

I entend backward compatibility in the sense as mangos has entry points that these entry points are used by other programs. So, if the entry points disapear, well you know what happens.

It's just a remark but in a devellopment of a software it's an important point that should not be set aside.

Learning project, it means learning all aspects of managing a devellopment project, this includes backward compatibilty. If you are not able understand that this is for the good of devs here well maybe return to your wiki definition :lol: or maybe try this one http://en.wikipedia.org/wiki/Noob.

As Mangos is a learning project, maybe devs should learn basics of devellopment just like Backward compatibility. As I saw many function changing names ou totally disapear in version update.

http://en.wikipedia.org/wiki/Backward_compatibility

It's just an improvement remark if you want to progress in dev world, no offense.

ok in that case can you give us a good mean to get a particular version of the sources on Git.

No problem to learn how to use this new tool, but I think most of us are disturbed to see such a tool which is not as easy to use as svn.

Personnaly I use other repository systems at work but all of them are more user friendly whith real interface not command line system.

Anyway, mangos is a learning project of course, but it concerns C++ not git

Welcome to a messy world...

As a lot of members here, I was using svn to checkout a particular version of the sources to apply patchs found in this forum and personal patchs, but now it seems to be impossible with this new source manager as we do not know the version we get.

As said before in this topic, is it possible to maintain both svn ang git repository?

I do not blame dev for changing repository as maybe it's easier for them, but most of other devs will be lost (as I am actually).

Thank you for your great job but please try to think about us poor windows devs.