all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Marius Bakke <marius@gnu.org>
Cc: wednesday <jessejohngildersleve@zohomail.eu>,
	Brett Gilio <brettg@gnu.org>,
	35516@debbugs.gnu.org
Subject: [bug#35516] [PATCH 0/1] gnu: emacs: Add lcms as an input.
Date: Thu, 07 Apr 2022 15:00:58 +0200	[thread overview]
Message-ID: <86zgkx120l.fsf_-_@gmail.com> (raw)
In-Reply-To: <87y2n7sgzs.fsf@gnu.org> (Marius Bakke's message of "Sat, 25 Jul 2020 18:21:11 +0200")

Hi,

Looking at old submission, it appears that

        <http://issues.guix.gnu.org/issue/35516>

had fallen into the cracks.


On Sat, 25 Jul 2020 at 18:21, Marius Bakke <marius@gnu.org> wrote:
> Brett Gilio <brettg@gnu.org> writes:
>> wednesday <jessejohngildersleve@zohomail.eu> writes:
>>
>>> There is not much of a need or reason for this, other than futher completing
>>> the TODO, which after this and my other patches I think may be complete. What
>>> adding this does is add a few elisp functions for converting to some formats,
>>> and working with lcms.
>>>
>>> wednesday (1):
>>>   gnu: emacs: Add lcms to inputs.
>>>
>>>  gnu/packages/emacs.scm | 2 ++
>>>  1 file changed, 2 insertions(+)
>>
>> Hi, I know this patch is quite old but our Emacs currently still does
>> not have LCMS support. LCMS was introduced in the 26 release, and I am
>> curious if anybody had any thoughts on adding this? From what I gather
>> 27 is due to be marked as stable any week now.
>
> No objections from me.  Emacs already has 'lcms' in its closure so there
> would be no size difference.

 Marius, since you have commit access, could you push this change?  And
thus close this. :-)


Cheers,
simon




  reply	other threads:[~2022-04-07 13:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30 22:25 [bug#35516] [PATCH 0/1] gnu: emacs: Add lcms as an input wednesday
2020-07-25  1:41 ` Brett Gilio
2020-07-25 16:21   ` Marius Bakke
2022-04-07 13:00     ` zimoun [this message]
2022-05-21 19:50     ` bug#35516: " 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

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

  git send-email \
    --in-reply-to=86zgkx120l.fsf_-_@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=35516@debbugs.gnu.org \
    --cc=brettg@gnu.org \
    --cc=jessejohngildersleve@zohomail.eu \
    --cc=marius@gnu.org \
    /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.