all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Tim Van den Langenbergh <tmt_vdl@gmx.com>
Cc: 42249-done@debbugs.gnu.org
Subject: bug#42249: [PATCH] gnu: Add font-libertinus.
Date: Thu, 09 Jul 2020 15:06:42 +0200	[thread overview]
Message-ID: <87wo3czvkt.fsf@nckx> (raw)
In-Reply-To: <trinity-028ea7db-ac40-4f11-8fa2-6ccb8c22f33b-1594135101235@3c-app-mailcom-bs03>

[-- Attachment #1: Type: text/plain, Size: 891 bytes --]

Tim,

Tim Van den Langenbergh 写道：
> I actually did switch to using a release URL instead of a git 
> fetch, but I forgot to update the patch, sorry about that! I 
> have added the updated patch.

I've pushed it as 5abed7ca3c611bbe30b59293f1837d62c08f05f4, with a 
copyright line for you and some synopsis/description fiddling 
(hope you don't mind).

Thank you very much!  This has replaced Libertine proper on my 
laptop now.

> Regarding the locale, my system (OpenSUSE) is running 
> en_GB.UTF-8, I can try building in a GuixSD VM if that helps?

Nah, the tarball worked fine so let's leave it at that.

Side note: we dropped the ‘SD’ a few years ago.  Now it's just 
‘Guix’ the package manager and ‘Guix System’ for entire operating 
systems.  It's been an enlightening lesson in how hard it is to 
rebrand things!  :-)

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

      parent reply	other threads:[~2020-07-09 13:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-07 15:18 [bug#42249] [PATCH] gnu: Add font-libertinus Tim Van den Langenbergh
2020-07-07 18:02 ` Tobias Geerinckx-Rice via Guix-patches via
2020-07-07 18:18   ` Tim Van den Langenbergh
2020-07-09 13:06 ` Tobias Geerinckx-Rice via Guix-patches via [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wo3czvkt.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=42249-done@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --cc=tmt_vdl@gmx.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.