Github messages for voidlinux
 help / color / mirror / Atom feed
From: Justinizer <Justinizer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: kleopatra:20.12.3
Date: Wed, 24 Mar 2021 07:00:51 +0100	[thread overview]
Message-ID: <20210324060051.943T8aexXQnuLyGjOHMFToqAN0BTdnQrTyqnGHf56zI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29605@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 753 bytes --]

New comment by Justinizer on void-packages repository

https://github.com/void-linux/void-packages/pull/29605#issuecomment-805506701

Comment:
> Would be nice to remove the INSTALL.msg and move to README.voidlinux, since it isn't urgent information.

Hmm personally I think this are urgent informations, because passphrases are an essential part to genrate keys. You can't generate keys without using passphrases, you can't import keys with passphrases etc.... So kleopatra without this would be a dummy.
This is similar to the vulkan driver for steam... You can use steam without it but there is no sense because 90% of the games need vulkan driver...

Edit: But I can move it to README.voidlinux if you want. Is this shown after an installation?

  parent reply	other threads:[~2021-03-24  6:00 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-20  4:05 [PR PATCH] " Justinizer
2021-03-20  5:17 ` cinerea0
2021-03-20 14:30 ` [PR REVIEW] " Johnnynator
2021-03-20 14:30 ` Johnnynator
2021-03-20 14:30 ` Johnnynator
2021-03-20 15:15 ` [PR PATCH] [Updated] " Justinizer
2021-03-20 15:17 ` [PR REVIEW] " Justinizer
2021-03-20 15:29 ` Justinizer
2021-03-20 15:32 ` Justinizer
2021-03-20 15:32 ` ericonr
2021-03-20 15:33 ` ericonr
2021-03-20 15:34 ` Justinizer
2021-03-20 15:43 ` Justinizer
2021-03-20 16:13 ` Johnnynator
2021-03-20 17:03 ` [PR PATCH] [Updated] " Justinizer
2021-03-20 17:04 ` Justinizer
2021-03-20 17:36 ` [PR REVIEW] " Justinizer
2021-03-21  5:43 ` sgn
2021-03-21  6:20 ` [PR PATCH] [Updated] " Justinizer
2021-03-21  6:46 ` Justinizer
2021-03-21  7:00 ` [PR REVIEW] " Justinizer
2021-03-21  7:22 ` sgn
2021-03-21  9:39 ` [PR PATCH] [Updated] " Justinizer
2021-03-21  9:47 ` Justinizer
2021-03-21 10:00 ` Justinizer
2021-03-21 10:04 ` sgn
2021-03-21 10:05 ` sgn
2021-03-21 10:15 ` [PR PATCH] [Updated] " Justinizer
2021-03-21 11:40 ` [PR REVIEW] " Johnnynator
2021-03-21 11:40 ` Johnnynator
2021-03-21 15:06 ` [PR PATCH] [Updated] " Justinizer
2021-03-21 15:10 ` Justinizer
2021-03-21 15:13 ` Justinizer
2021-03-21 15:26 ` Justinizer
2021-03-21 15:28 ` Justinizer
2021-03-21 15:39 ` Justinizer
2021-03-21 15:55 ` Justinizer
2021-03-21 16:32 ` Justinizer
2021-03-21 17:00 ` [PR PATCH] [Merged]: " Johnnynator
2021-03-24  0:34 ` ericonr
2021-03-24  5:19 ` Justinizer
2021-03-24  6:00 ` Justinizer [this message]
2021-03-24 11:42 ` ericonr
2021-03-24 19:06 ` Justinizer
2021-03-24 19:08 ` ericonr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210324060051.943T8aexXQnuLyGjOHMFToqAN0BTdnQrTyqnGHf56zI@z \
    --to=justinizer@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).