From: Oleg Pykhalov <go.wigust@gmail.com>
To: rdes <rdes@protonmail.com>
Cc: 45108-done@debbugs.gnu.org
Subject: bug#45108: Added emacs-burly
Date: Tue, 08 Dec 2020 08:01:32 +0300 [thread overview]
Message-ID: <87pn3k99hv.fsf@gmail.com> (raw)
In-Reply-To: <nCN82e_FRUxyoeHVqEwJ7AEDrg5SaTbVMJ6fDa-QVkadSuv3jRFTSJ9dKP4shhbHS7ACcyZ78Tj5eDJPPOblZjoSihDdNemyXuRuRbvTqZU=@protonmail.com> (rdes via Guix-patches via's message of "Mon, 07 Dec 2020 23:31:41 +0000")
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
Hello,
Thank you for patches.
rdes via Guix-patches via <guix-patches@gnu.org> writes:
[…]
> Please let me know in the future if this should be multiple emails.
It's a good practice to split an email with multiple patches, which is
described on webpage “Sending a Patch Series” [1].
[1] https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html
> Sent with [ProtonMail](https://protonmail.com) Secure Email.
> From 0e24818db4f22cff0d841b7b77866121e0f2d6a5 Mon Sep 17 00:00:00 2001
> From: Ryan Desfosses <rdes@protonmail.com>
> Date: Mon, 7 Dec 2020 18:17:52 -0500
> Subject: [PATCH 1/2] gnu: Add emacs-map
^
missing dot
[…]
> + (synopsis "Map manipulation functions")
> + (description
> + "map.el provides map-manipulation functions that work on alists,
> +hash-table and arrays. All functions are prefixed with \"map-\".")
1. “description should start with an upper-case letter or digit” as
reported by "./pre-inst-env guix lint".
2. Istead of ‘\"map-\"’, please use ‘@code{map-}’.
[…]
> Subject: [PATCH 2/2] gnu: Add emacs-burly
^
missing dot
Pushed with changes above to master.
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2020-12-08 5:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 23:31 [bug#45108] Added emacs-burly rdes via Guix-patches via
2020-12-08 5:01 ` Oleg Pykhalov [this message]
2020-12-08 7:23 ` Nicolas Goaziou
2020-12-08 8:59 ` Oleg Pykhalov
2020-12-08 20:43 ` Michael Rohleder
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=87pn3k99hv.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=45108-done@debbugs.gnu.org \
--cc=rdes@protonmail.com \
/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.