From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Brian Kubisiak <brian@kubisiak.com>, 55693@debbugs.gnu.org
Subject: [bug#55693] [PATCH 0/2] gnu: Add gitlint.
Date: Sun, 05 Jun 2022 23:19:34 +0200 [thread overview]
Message-ID: <87k09uerkp.fsf_-_@gnu.org> (raw)
In-Reply-To: <93a6870b8289510c35c014974f9e23cd0fa32e0f.camel@telenet.be> (Maxime Devos's message of "Thu, 02 Jun 2022 01:04:30 +0200")
Hi,
Maxime Devos <maximedevos@telenet.be> skribis:
> Input labels aren't required anymore. Try running "guix style -S
> inputs". Also, IIUC, Hartmut Goebel would prefer not using quasiquote
> (`):
>
> (arguments
> (list #:phases
> #~(modify-phases [stuff]
> [stuff]
> ...)))
>
> to avoid the complicated quasiquote/unquote construct, with which I
> agree though it's AFAIK not (yet?) elevated to ‘official Guix style’ or
> such.
I too prefer:
(list #:foo #~(…))
over:
`(#:foo ,#~(…))
Otherwise that’s too much line noise IMO, especially for a newcomer.
Ludo’.
next prev parent reply other threads:[~2022-06-05 21:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 23:53 [bug#55693] [PATCH 0/2] gnu: Add gitlint Brian Kubisiak
2022-05-28 23:55 ` [bug#55693] [PATCH 1/2] gnu: python-sh: Update to 1.14.2 Brian Kubisiak
2022-05-28 23:55 ` [bug#55693] [PATCH 2/2] gnu: Add gitlint Brian Kubisiak
2022-05-29 10:51 ` Maxime Devos
2022-05-29 21:37 ` Brian Kubisiak
2022-05-29 21:43 ` Maxime Devos
2022-05-30 23:17 ` [bug#55693] [PATCH v2 1/2] gnu: python-sh: Update to 1.14.2 Brian Kubisiak
2022-05-30 23:17 ` [bug#55693] [PATCH v2 2/2] gnu: Add gitlint Brian Kubisiak
2022-06-01 23:04 ` Maxime Devos
2022-06-05 21:19 ` Ludovic Courtès [this message]
2022-06-02 1:56 ` [bug#55693] [PATCH v3 1/2] gnu: python-sh: Update to 1.14.2 Brian Kubisiak
2022-06-05 21:25 ` bug#55693: [PATCH 0/2] gnu: Add gitlint Ludovic Courtès
2022-06-02 1:56 ` [bug#55693] [PATCH v3 2/2] " Brian Kubisiak
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=87k09uerkp.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=55693@debbugs.gnu.org \
--cc=brian@kubisiak.com \
--cc=maximedevos@telenet.be \
/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).