From: Cayetano Santos via Guix-patches via <guix-patches@gnu.org>
To: control@debbugs.gnu.org,74231@debbugs.gnu.org
Subject: [bug#74231] QA review for 74231
Date: Thu, 07 Nov 2024 12:40:49 +0100 [thread overview]
Message-ID: <87ed3n1dby.fsf@inventati.org> (raw)
In-Reply-To: <578f2ae3ba7cc4838ffdbc0929e6d3a5c8a6a9cc.1730918803.git.suhail@bayesians.ca>
user guix
usertag 74231 + waiting-on-contributor
thanks
Guix QA review form submission:
"The Elisp dependencies of Emacs packages are typically provided as
propagated-inputs when required at run time."
See: https://guix.gnu.org/manual/en/html_node/Emacs-Packages.html.
To note that this is a completely different beast compared to previous
package (repo, version and mantainer).
Items marked as checked:
- Commit messages
- Package builds
- Lint warnings
- Package style
- Dependent packages build
next prev parent reply other threads:[~2024-11-07 11:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 18:37 [bug#74231] [PATCH] gnu: emacs-git-email: Update to 0.5.0 Suhail Singh
2024-11-06 18:37 ` [bug#74231] [PATCH v2] gnu: emacs-git-email: Update to 0.6.0 Suhail Singh
2024-11-15 7:41 ` bug#74231: " Liliana Marie Prikler
2024-11-07 11:40 ` Cayetano Santos via Guix-patches via [this message]
2024-11-07 13:32 ` [bug#74231] QA review for 74231 Suhail Singh
2024-11-07 15:13 ` Cayetano Santos via Guix-patches via
2024-11-07 15:48 ` emacs-git-email: Guix policy for dealing with abandoned packages with active forks (was: [bug#74231] QA review for 74231) Suhail Singh
2024-11-07 16:08 ` emacs-git-email: Guix policy for dealing with abandoned packages with active forks Suhail Singh
2024-11-07 16:20 ` [bug#74231] " Cayetano Santos via Guix-patches via
2024-11-07 16:20 ` Cayetano Santos
2024-11-11 2:45 ` [bug#74231] " Liam Hupfer
2024-11-11 2:45 ` Liam Hupfer
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=87ed3n1dby.fsf@inventati.org \
--to=guix-patches@gnu.org \
--cc=74231@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
--cc=csantosb@inventati.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.