You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2022. It is now read-only.
If you run pijul key, it does not print anything. I think it should print that a subcommand is missing and required. Related to this, https://pijul.org/manual/signing_patches.html is outdated. It uses subcommand keys, as in pijul keys --generate-signing, whereas it is actually key. With the latest version, that would be pijul key gen --signing.
The naming convention is kind of odd to me as well. For example:
pijul [SUBCOMMAND], AND pijul key [SUBCOMMAND]. Wouldn't it be better to use COMMAND for everything that isn't actually a subcommand? Let me know what you think.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If you run
pijul key
, it does not print anything. I think it should print that a subcommand is missing and required. Related to this, https://pijul.org/manual/signing_patches.html is outdated. It uses subcommandkeys
, as inpijul keys --generate-signing
, whereas it is actuallykey
. With the latest version, that would bepijul key gen --signing
.The naming convention is kind of odd to me as well. For example:
pijul [SUBCOMMAND]
, ANDpijul key [SUBCOMMAND]
. Wouldn't it be better to useCOMMAND
for everything that isn't actually a subcommand? Let me know what you think.The text was updated successfully, but these errors were encountered: