all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Andrew Patterson <andrewpatt7@gmail.com>
Cc: conses <contact@conses.eu>,
	62806@debbugs.gnu.org, Andrew Tropin <andrew@trop.in>
Subject: [bug#62806] [PATCH] gnu: home: services: fontutils: Add support for SXML fragments.
Date: Thu, 11 May 2023 14:34:54 +0200	[thread overview]
Message-ID: <87o7mr3v2p.fsf_-_@gnu.org> (raw)
In-Reply-To: <87wn20dc7t.fsf@gmail.com> (Andrew Patterson's message of "Mon, 24 Apr 2023 19:24:31 -0400")

Hi Andrew,

Sorry for the delay and thanks for your feedback.

Andrew Patterson <andrewpatt7@gmail.com> skribis:

> It seems to me that the main options are:
> 1) Just use my patch, or
> 2) write a new patch with an actual configuration record type,
>   based on conses and Taiju HAGASHI's patches, either with
>   a) a single font family for the default font family settings,
>   b) a list of font families for the default font families, or
>   c) allowing either.

I went with #1, but that doesn’t prevent us from considering #2 as an
improvement going forward.  Conses, Andrews: you’re welcome to share
your thoughts!

> If we don't want to just use my patch, I can work on a new patch
> with a configuration record.  How do you print a deprecation
> warning?

The (guix deprecation) module provides facilities for that.  If that’s
too restrictive, use ‘warning’ from (guix diagnostics).

Thanks!

Ludo’.




  reply	other threads:[~2023-05-11 12:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-13  3:40 [bug#62806] [PATCH] gnu: home: services: fontutils: Add support for SXML fragments Andrew Patterson
2023-04-24 20:41 ` Ludovic Courtès
2023-04-24 23:24   ` Andrew Patterson
2023-05-11 12:34     ` Ludovic Courtès [this message]
2023-05-12  6:45       ` Andrew Tropin
2023-05-18  9:11         ` Miguel Ángel Moreno

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=87o7mr3v2p.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=62806@debbugs.gnu.org \
    --cc=andrew@trop.in \
    --cc=andrewpatt7@gmail.com \
    --cc=contact@conses.eu \
    /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.