 |
This does not need to be tied to 2.10 |
|
|
This appears to be done? https://github.com/stgatilov/darkmod_src |
 |
Hmm.... Yes, it works. I think I won't write any PR-accepting scripts. What I should do is add GitHub-specific readme, which includes description and how to get third-party artefacts. |
 |
Curious. Why continue using SVN and not GitHub as the official repo? |
|
|
Crap... I guess we need some kind of wiki page listing the reasons why we don't use git =( And add a small section that if we start collecting donations, then we can "finally" switch to Perforce and live like pro-s =) |
|
|
Not a fan of Git, I take it. haha :) The main reason I asked was that I think it would be easier to collaborate. Maybe not for the core team members, though? Over the past several months, I've created my own workflow, so I'm used to it now. It is a bit cumbersome to post diffs to the forum, but it's not terrible. Yes, I think some info about not using Git would be helpful on the first post of the "Public access to development versions" thread. |
|
|
Since the core task is done and is not really a 2.11 blocker, I will mark this as resolved. |
|
|
Daft Mugi, you can try(!) to create a PR against GitHub mirror. I think it would be possible to merge such PRs into SVN manually (or even do that in separate git-svn repo). |
|
|
One thing I would suggest is that the compile command be changed to: make -j$(nproc) in COMPILING.txt Some distros do a bad job of constraining resources when you don't specify the upper limit of cores and this can make the system unresponsive during compile. |
- Anonymous
