From: "Clément Lassieur" <clement@lassieur.org>
To: Steve George <steve@futurile.net>
Cc: 67123@debbugs.gnu.org
Subject: [bug#67123] [PATCH v2 0/1] gnu: Add pass-coffin
Date: Sat, 24 Feb 2024 11:23:17 +0100 [thread overview]
Message-ID: <87v86e40ve.fsf@lassieur.org> (raw)
In-Reply-To: <cover.1708763265.git.steve@futurile.net> (Steve George's message of "Sat, 24 Feb 2024 08:39:33 +0000")
On Sat, Feb 24 2024, Steve George wrote:
> Review by Steve George:
> * submission: checked commit format, synopsis and commit
> * submission: license, patch applies cleanly
> * functionality: test installed, guix lint is clean
> * code: checked style
> * added: Reviewed-by commit trailer
> * re-roll to trigger QA build
>
> * Question for committer: this is an add-on to password-store and can't be
> used without it. Should password-store be a propagated-input?
I don't think so. See emacs for example. That would make it harder to
use another version of password-store.
> Christian Miller via Guix-patches via (1):
> gnu: Add pass-coffin
>
> gnu/packages/password-utils.scm | 32 ++++++++++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
>
>
> base-commit: e7990b12170eec0c35541196f948be26a9e4a519
next prev parent reply other threads:[~2024-02-24 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 18:41 [bug#67123] [PATCH] gnu: Add pass-coffin Christian Miller via Guix-patches via
2024-02-24 8:39 ` [bug#67123] [PATCH v2 0/1] " Steve George
2024-02-24 8:39 ` [bug#67123] [PATCH v2 1/1] " Steve George
2024-02-24 10:23 ` Clément Lassieur [this message]
2024-02-26 15:51 ` bug#67123: Close Andreas Enge
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v86e40ve.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=67123@debbugs.gnu.org \
--cc=steve@futurile.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).