Update several support files

[Fanatic-64]

Update several non-source files, including:
-Documentation
-A newer CHT
-Jabo 1.6.1 plugins (instead of 1.6)
-N-Rage 1.83 (instead of 1.82a)

[Fanatic-64]

Don't know how to make both commits into separate pull requests...

[death-droid]

Have to keep changes separated into individual branches.

[Fanatic-64]

Will do... next time. Don't know how to roll back commits either.

[blikblum]

Create a branch from a previous commit http://stackoverflow.com/questions/2816715/branch-from-a-previous-commit-using-git
Cherrypick the commit into this branch https://ariejan.net/2010/06/10/cherry-picking-specific-commits-from-another-branch/
Create a new pull request from the branch

[project64]

where is the source of the binary files from? I pushed a change for the 400 ai

[Fanatic-64]

You mean where I got them from? Well, here's were I got all the files from:
-PJ64gameFAQ.chm, RDB - WhatsNew.txt: Obtained from here: http://www.pj64-emu.com/downloads/func-startdown/109/
-Project64.cht: Obtained from this commit: https://github.com/project64/project64/tree/e815584b593d2b2c715a89b8a7d4321c8c1106ce
-NRage_DInput8_V2.dll, N-Rage - Readme.txt: Obtained from here: http://members.chello.at/n-rage/dinput8/index.html Source code is available there.
-Jabo_Direct3D8.dll, Jabo_Dsound.dll, Jabo_DInput.dll: Obtained from here: http://www.jabosoft.com/articles/114

[Fanatic-64]

Is this going to be merged? I need to delete and recreate my fork since I messed a bit with GitHub.

[LegendOfDragoon]

Why delete?

[Fanatic-64]

"and recreate my fork since I messed a bit with GitHub"

[LegendOfDragoon]

You're likely able to fix it without having to delete ;/ . You can edit commit history. To make your fork up to date, just use type the following, into git shell
cd project64
git pull https://github.com/project64/project64.git in the git cmd.

I think you'll have to wait until this pull request is accepted, since I believe git pull overwrites your files.

[cxd4]

That would pull the current state of project64/project64.git to his local hard disk yes, but it wouldn't revert the commits already uploaded to Fanatic-64/project64.git to his online account.

I've deleted and re-forked Project64 repository 3 times already and guess I didn't see any negative effects from it. I had to delete and re-fork whenever a pull request I sent wasn't merged, and force-overwriting master branch when pushing failed 90% of the time due to my crappy network Wi-Fi.

To be on the topic of the pull request, I can't make anything of this hardly since Git isn't really for hosting binary files either. It's better to work with text commits. The binary files / support plugins, DLLs, CHMs should probably just be given in the package downloads for public users.

[project64]

ok I think that has everything from this pull request now has bee updated or removed from the release.

Any issues with me closing it?

[Fanatic-64]

Could we include the newer RDB - WhatsNew.txt file? Or remove it from the repo?

[project64]

there has been a lot of updates to the rdb lately .. what in particular do you want in there ?

yes some of these files can probably removed from the current branch.

[oddMLan]

Where is the newer .cht file from? Is that update going to be included in master repo?

[project64]

as Fanatic-64 comment, I got it from https://github.com/project64/project64/tree/e815584b593d2b2c715a89b8a7d4321c8c1106ce it is now in the config dir

[death-droid]

Can be closed now?

[project64]

I suspect we can, I removed the old files that will not be in 2.2, the change to the settings config is in as well as I think all files that were updated.