unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Philip McGrath <philip@philipmcgrath.com>
Cc: 53131-done@debbugs.gnu.org
Subject: bug#53131: [PATCH 0/4] Update Fira fonts.
Date: Thu, 13 Jan 2022 23:03:56 +0100	[thread overview]
Message-ID: <871r1b70oj.fsf@gnu.org> (raw)
In-Reply-To: <20220108234449.149435-1-philip@philipmcgrath.com> (Philip McGrath's message of "Sat, 8 Jan 2022 18:44:49 -0500")

Hi,

Philip McGrath <philip@philipmcgrath.com> skribis:

> These patches update 'font-fira-sans', adjust the definition of
> 'font-fira-mono' to inherit from 'font-fira-sans', and update
> 'font-fira-code'.

Nice.

> The final patch adds a note to 'font-fira-go' to explain that it does not have
> corresponding source code: that patch is last, in case the FSDG require that
> 'font-fira-go' be removed, instead.

I believe that is fine (there are other font packages that lack
“source”).

>   gnu: font-fira-sans: Update to 4.203.
>   gnu: font-fira-mono: Inherit from font-fira-sans.
>   gnu: font-fira-code: Update to 6.2.
>   gnu: font-fira-go: Note lack of corresponding source.

Applied, thanks!

Ludo’.




      parent reply	other threads:[~2022-01-13 22:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-08 23:44 [bug#53131] [PATCH 0/4] Update Fira fonts Philip McGrath
2022-01-08 23:47 ` [bug#53131] [PATCH 1/4] gnu: font-fira-sans: Update to 4.203 Philip McGrath
2022-01-08 23:47   ` [bug#53131] [PATCH 2/4] gnu: font-fira-mono: Inherit from font-fira-sans Philip McGrath
2022-01-08 23:47   ` [bug#53131] [PATCH 3/4] gnu: font-fira-code: Update to 6.2 Philip McGrath
2022-01-08 23:47   ` [bug#53131] [PATCH 4/4] gnu: font-fira-go: Note lack of corresponding source Philip McGrath
2022-01-13 22:03 ` Ludovic Courtès [this message]

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=871r1b70oj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=53131-done@debbugs.gnu.org \
    --cc=philip@philipmcgrath.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).