Added -P flag to oclvanityminer usage (already supported) - #42
Open
jgbreezer wants to merge 1 commit into
Open
Conversation
Author
|
Excuse the open/close state confusion, first time I've done a pull request. |
|
Samr7 hasn't been active with this repo. I've already merged a similar change in my fork at https://github.com/WyseNynja/vanitygen. It's easy to install with my brew tap at https://github.com/WyseNynja/homebrew-bitcoin |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There were some minor gripes in the bitcointalk forum threads earlier on (I've just been getting into this and started address-mining on my AMD Radeon), about the -P of both ocl and plain vanitygen; the ocl program doesn't list -P in its usage though it works (or acts like it does).