Also, for the all those with the RMS SDK up as public repo's, you may want to read the comments in top 40 or so lines of each of those files.
It you get yourselves a paid GitHub account you can set up a private repo for the SDK (and any other libraries you use, but don't have the right to redistribute) then bring these into your project as submodules. It's a super nice workflow to tag the official AMX releases with their version number so your projects checkout these rather than the branch HEAD. When the version bumps you just checkout the new version in any of your projects you want to use it in and your good to go, if an API update breaks anything, no stress, you can continue using the old version while the repo moves on. You're then free to build your own extensions in branches which you can continue to rebase as the core code moves. Gives you all the niceties (release diffing, proper dependancy management etc), without all the potential legal issues.
Comments
I use git and love it already. But, this really makes it extra-special-sauce.
It you get yourselves a paid GitHub account you can set up a private repo for the SDK (and any other libraries you use, but don't have the right to redistribute) then bring these into your project as submodules. It's a super nice workflow to tag the official AMX releases with their version number so your projects checkout these rather than the branch HEAD. When the version bumps you just checkout the new version in any of your projects you want to use it in and your good to go, if an API update breaks anything, no stress, you can continue using the old version while the repo moves on. You're then free to build your own extensions in branches which you can continue to rebase as the core code moves. Gives you all the niceties (release diffing, proper dependancy management etc), without all the potential legal issues.