all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Brett Gilio <brettg@gnu.org>
To: Jack Hill <jackhill@jackhill.us>
Cc: 42736@debbugs.gnu.org
Subject: [bug#42736] [PATCH] gnu: emacs-doom-themes: Update to 2.1.6-5.
Date: Fri, 07 Aug 2020 13:10:43 -0500	[thread overview]
Message-ID: <87ft8y5nto.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2008070019470.4809@marsh.hcoop.net> (Jack Hill's message of "Fri, 7 Aug 2020 00:28:55 -0400 (EDT)")

Jack Hill <jackhill@jackhill.us> writes:

> On Thu, 6 Aug 2020, Brett Gilio wrote:
>
>>
>> Hey Jack,
>>
>> Thanks for taking time to revise this package. When I originally wrote
>> it I made notice to the fact that some elisp bytecompilations were
>> failing or not behaving appropriately. Since then I am pretty sure
>> hlissner has disabled the bytecompilation completely? Could you review
>> this for me, and if true please revise the appropriate arguments. If you
>> aren't sure what I am talking about, please let me know.
>
> Brett,
>
> I saw your lovely comment, but in my excitement that the update solved
> the problem I was having with Emacs 27 compatibility, I didn't think
> too hard about it.
>
> I believe that I understand what you're asking. I'll take a look
> tomorrow to see if we should change the package definition in light of
> upstream changes. If I get stuck, I'll be sure to let you know.
>
> Best,
> Jack

Sounds great! Thanks.




  reply	other threads:[~2020-08-07 18:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-07  3:17 [bug#42736] [PATCH] gnu: emacs-doom-themes: Update to 2.1.6-5 Jack Hill
2020-08-07  3:37 ` Brett Gilio
2020-08-07  4:28   ` Jack Hill
2020-08-07 18:10     ` Brett Gilio [this message]
2020-08-08  2:09       ` Jack Hill
2020-08-08  2:27         ` Brett Gilio
2020-08-08  2:40           ` Jack Hill
2020-08-08  2:11 ` [bug#42736] [PATCH v2] " Jack Hill
2020-08-08  2:29   ` bug#42736: " Brett Gilio

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=87ft8y5nto.fsf@gnu.org \
    --to=brettg@gnu.org \
    --cc=42736@debbugs.gnu.org \
    --cc=jackhill@jackhill.us \
    /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.