Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented Mar 30, 2014

This was really out dated, i re-wrote for the pool i run and thought i would just paste it here as well.

This was really out dated, i re-wrote for the pool i run and thought i would just paste it here as well.
@ghost
Copy link
Author

ghost commented Mar 30, 2014

This should reduce your support requests :/ :+1:

@TheSerapher
Copy link
Contributor

Maybe an external entry might be better for all this? It's a pretty big topic and just throwing a few command lines at people may not be enough. It is better than what we have though, so I'll merge it.

TheSerapher added a commit that referenced this pull request Mar 30, 2014
@TheSerapher TheSerapher merged commit d0c40ba into MPOS:master Mar 30, 2014
@ghost
Copy link
Author

ghost commented Mar 30, 2014

I updated it, It needs to be merged again.

@TheSerapher
Copy link
Contributor

Too late, once a merge is done, you have to re-create a PR. Only existing PRs can be merged again.

Again it was directed at master, that was a mistake on my part to merge it. Can you please ensure you target development branch in MPOS?

@ghost
Copy link
Author

ghost commented Mar 30, 2014

Sorry about that, But i will push the next one to master.. Just because its better then the original.. and will work for scrypt and sha256.

@TheSerapher
Copy link
Contributor

No, I accepted by accident. Push to Dev, master is NOT our development branch and all changes are tested through development pools.

@TheSerapher
Copy link
Contributor

If you are on your own fork make sure to sync it with upstream first: https://help.github.com/articles/syncing-a-fork

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants