From: Bruno Victal <mirai@makinata.eu>
To: Jake Leporte <jakeleporte@outlook.com>
Cc: 60827@debbugs.gnu.org
Subject: [bug#60827] [PATCH v3] gnu: Add dozenal.
Date: Mon, 23 Jan 2023 23:24:23 +0000 [thread overview]
Message-ID: <d5ea307a-3d48-3c83-cf65-9e327ee5d09e@makinata.eu> (raw)
In-Reply-To: <MN2PR20MB2605C37DBE956CB9A6D6886CACC89@MN2PR20MB2605.namprd20.prod.outlook.com>
On 2023-01-23 22:43, Jake Leporte wrote:
> Got it- thanks for the correction! I've re-written the patch to use G-Exps.
>
> The `guix style`-reccomended changes involved writing #$output:gui as (ungexp
> output "gui"), and various indentation changes that made some of the
> 'split-output code tough to read, in my opinion, so this patch deviates from
> those recommendations a bit. Let me know if you'd rather I take the `guix
> style` output directly.
Sometimes guix style can make things worse, there's no problem in deviating from it
as long it doesn't result in a worse formatting.
Cheers,
Bruno
next prev parent reply other threads:[~2023-01-23 23:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 4:44 [bug#60827] [PATCH 0/3] Add perl-par, xforms, and dozenal package definitions Jake Leporte
2023-01-16 1:09 ` [bug#60827] [PATCH 0/4] Updated: Add dozenal plus dependencies Jake Leporte
2023-01-16 1:11 ` [bug#60827] [PATCH 1/4] gnu: Add perl-par Jake Leporte
2023-01-23 21:02 ` [bug#60827] [PATCH v2] gnu: Add dozenal Jake Leporte
2023-01-23 21:38 ` Bruno Victal
2023-01-23 22:43 ` [bug#60827] [PATCH v3] " Jake Leporte
2023-01-23 23:24 ` Bruno Victal [this message]
2023-01-24 7:02 ` ( via Guix-patches via
2023-01-27 2:16 ` [bug#60827] [PATCH v4] " Jake Leporte
2023-02-18 0:31 ` [bug#60827] [PATCH v5 1/4] gnu: Add perl-par Jake Leporte
2023-02-27 0:39 ` [bug#60827] [PATCH v6 0/4] Add dozenal and dependencies Jake Leporte
2023-03-06 12:47 ` [bug#60827] [PATCH v7 1/4] gnu: Add perl-par Jake Leporte
2023-03-22 1:44 ` [bug#60827] [PATCH 0/3] Add perl-par, xforms, and dozenal package definitions Maxim Cournoyer
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=d5ea307a-3d48-3c83-cf65-9e327ee5d09e@makinata.eu \
--to=mirai@makinata.eu \
--cc=60827@debbugs.gnu.org \
--cc=jakeleporte@outlook.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 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).