-
Notifications
You must be signed in to change notification settings - Fork 38.6k
doc: Add gpg key import instructions for Windows #23916
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
contrib/builder-keys/README.md
Outdated
| To fetch keys of builders and active developers, feed the list of fingerprints | ||
| of the primary keys into gpg: | ||
|
|
||
| using \*NIX: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: it's more usual to say "on UNIX" and "on Windows", instead of "using"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Accepted and applied.
Co-authored-by: Michael Ford <[email protected]>
OS designations slightly more understandable.
|
You'll need to squash this to a single commit. |
That is not possible on the website, is it? |
No idea, maybe check the documentation: https://docs.github.com/en. When you're done the commit message should be |
|
I will make a new pull request with a single commit. The only loss (though I suppose it's recorded here) is that I don't think @fanquake 's help will be attributed. |
|
New PR is #24788 |
|
I wish github did either of two things:
|
I propose this change so that Windows users can more easily import signers' keys.