Adding documentation for this to tldr-pages; anything you'd like to change? #98
Comments
|
This is neat! Thanks for submitting that PR! Maybe also add an example where the public key is provided on the command line for verification? minisign -P <base64 encoded public key> -Vm <file>Maybe not if you think this is too much. But this is probably the most common way to do verification as the entire command can be copy/pasted from a project's documentation, and verification can be immediately done without requiring a public key file. |
|
Alright, sounds fair; just did that. I don't think that's too much ‒ 4 to 8 examples are allowed, I was at four, so a fifth won't hurt, I guess. Should this issue be closed now or is there anything else you'd like to add? |
|
@FantasyCookie17 let me me a correction: not 4 to 8, but 1 to 8 are allowed ;) |
|
Oh 😸 I must've misremembered something then. For reference:
https://github.com/tldr-pages/tldr/blob/master/CONTRIBUTING.md |
|
Since the conversation moved over to the tldr repo, I'm closing this for now. |
* Added English and German pages for Minisign * Fixed typo * Fixed the remaining typos * Apply suggestions by bl-ue * Forgot to add English page to last commit * Change description to official description * Add suggestion by jedisct1; see jedisct1/minisign#98 * Apply changes requested by bl-ue * Patch German translation * Forgot "encoded" * Make order of flags more consistent as suggested by jedisct1 * Forgot to add German translation in last commit * Use relative instead of absolute paths * Shorten comments * Change German translations to imperative * Fix spelling mistake * Use imperative in German translation in all commands * Use Umlaute in German translation even in arguments * Use 'ü' in 'schluessel'
I didn't really find any other way to contact you, so I decided to open an issue here instead… I opened a PR at tldr-pages/tldr#5757 to add documentation for Minisign to tldr. If there's anything you'd like to change or add about it, you might want to have a look over there.
The text was updated successfully, but these errors were encountered: