all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Switching to Artifex Ghostscript
Date: Sat, 03 Jun 2017 15:55:33 +0200	[thread overview]
Message-ID: <87r2z1kwfe.fsf@gnu.org> (raw)
In-Reply-To: <20170602181616.GA8336@jasmine> (Leo Famulari's message of "Fri, 2 Jun 2017 14:16:16 -0400")

Leo Famulari <leo@famulari.name> skribis:

> On Fri, Jun 02, 2017 at 12:26:12PM -0400, Leo Famulari wrote:
>> On Mon, May 29, 2017 at 06:14:57PM -0400, Leo Famulari wrote:
>> > How should we make this transition? Should we add Artifex Ghostscript
>> > and transition packages over to it, wait for the next core-updates, or
>> > something else?
>> 
>> Any opinions? Otherwise, I'll put it on the next core-updates branch, unless the
>> current branch is still "open for business".
>
> After discussing it with Ludo on IRC, I pushed to core-updates as
> 55af10fb987ce96966850da08f8f8d12691dee63.

Thank you!

Ludo’.

  reply	other threads:[~2017-06-03 13:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-20 20:55 Switching to Artifex Ghostscript Leo Famulari
2017-05-20 21:53 ` Marius Bakke
2017-05-21 13:06   ` Ricardo Wurmus
2017-05-23 17:39     ` Leo Famulari
2017-05-26 12:02       ` Ricardo Wurmus
2017-05-23 20:42     ` Ludovic Courtès
2017-05-29 17:50       ` Leo Famulari
2017-05-29 18:33         ` Leo Famulari
2017-05-29 18:38         ` Ricardo Wurmus
2017-05-29 20:47           ` Leo Famulari
2017-05-29 22:14           ` Leo Famulari
2017-06-02 16:26             ` Leo Famulari
2017-06-02 18:16               ` Leo Famulari
2017-06-03 13:55                 ` Ludovic Courtès [this message]
2017-05-29 23:22           ` Mark H Weaver
2017-05-30  4:40             ` Leo Famulari

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=87r2z1kwfe.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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.