Move to GitHub

[bearbin]

Gti submodules update automatically, you just have to use the recursive option when you pull AFAIK - git pull -r as opposed to git pull.

[xoft]

"pull -r" is the same as "pull --rebase", not recursive.

---

Oh, there is "--recurse-submodules".

---

Okay then, if you can get the submodules working and write up a guide on how to use this properly, do it.

[bearbin]

I'll try and get them working

---

I've pushed up a branch with it, I'll write a guide about it.

[xoft]

The guide is still missing. I'm expecting something along the lines of a howto: what to do when I want to commit to a plugin, what to do if i want to update the server but have local changes in the plugin, what to do when I want to pull server and plugin changes when I don't have any local modifications, and possibly troubleshooting.

[bearbin]

Ok, if you want to work on a plugin, all you need to do is go into the plugin directory, make your changes, commit and push. It's a git repo inside another. You don't need to care about updating the server if you have plugin mods, just pull without the recursive option. If you don't have any modifications, pull as normal.

[xoft]

The submodules are having a problem. I cannot clone them, because on Windows I use the http:// access method, but submodules require git:// access method.

[bearbin]

Can you use ssh? If so, I'll change them to that, if not then I'll change them to HTTP.

[xoft]

It is set to ssh right now. I guess I could set it up, though SSH key work has always scared me. This crypto stuff is just so... cryptical

[bearbin]

Setting up ssh is probably sensible, but idk. It may be way harder on windows than linux.

[NiLSPACE]

One thing I realy hate about github is that on mobiles the normal website loading speed is realy slow, and the mobile version is realy feature-less.