Bring project up to date

[tlindner]

I would like to start sending this repository pull requests for any future contributions. But first I would need this repo to be brought into line with the current version on Source Forge.
Almost every file is changed because there was a re-lint done. Then there are the 2 bug fixes which I did recently.
I'm not sure the best way to manage all this.

[n6il]

I don't remember exactly how I did this before. Perhaps hg-git or similar? Let me look into it and get back to you.

[DrPitre]

There's this repository (https://github.com/boisy/toolshed-new) which has all of the latest changes from the SourceForge repo along with an updated README.md.

[bluearcus]

Now we have a live upto-the-minute toolshed repo in the nitros9 project, can this one at least be flagged as not the latest and do not use in the README? And a link to the definitive master repo provided?

The number of times I tell someone, just use toolshed, and then they come back with a problem because they've used this repo, rather than the master, complete with built binaries, is getting too many to count.