@cbuchner1:

Awesome fracking work with scrypt-jane man!

May I make a developer suggestion?  Could you "branch" in Github, away from the master, the next time you want to experiment and upgrade code?  It was quite difficult to find stable scrypt versions during this last endeavor.  Ping me in PM and I can help ya out on github branch management, and how to submit pull requests to merge it back into the master.  It's actually quite simple.

In short, leave the master alone: calling it your "stable" releases.  Branch for any possible changes, upgrades, or even hotfixes with "git checkout -b".  Nothing to download, and you are now on a new branch.  Once it's fixed, patched, etc and you are read, submit a Pull request to the master, and then go approve the Pull request - BAM now you have the latest in master.

It would keep those of us that like to tinker with your code, to only tinker with the "stable" master branch - while you merge in hotfixes and big new algorithms.  

Thanks again man!


Now, to get me some Jane!