all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Hilton Chain <hako@ultrarare.space>, 65478-done@debbugs.gnu.org
Cc: Andrew Tropin <andrew@trop.in>
Subject: bug#65478: [PATCH emacs-team v3] build: emacs-utils: Adjust `emacs-compile-directory' for Emacs 29.
Date: Sat, 09 Sep 2023 10:23:23 +0200	[thread overview]
Message-ID: <df4f934b7db60fd810b64fc6216c7fdd27b2edb8.camel@gmail.com> (raw)
In-Reply-To: <19403aa2ad67bd0cd4d35cf0b3332d1c18b1a197.camel@gmail.com>

Am Freitag, dem 01.09.2023 um 21:37 +0200 schrieb Liliana Marie
Prikler:
> will wait for CI before pushing, however.
Looks like CI doesn't know whether it ought to build stuff; pushed as
it LGTM.

Cheers




      reply	other threads:[~2023-09-09  8:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23 18:00 [bug#65478] [PATCH emacs-team] gnu: emacs-flim-lb: Explicitly compile files to bytecode Hilton Chain via Guix-patches via
2023-08-27  6:24 ` Liliana Marie Prikler
2023-08-27 12:52   ` Hilton Chain via Guix-patches via
2023-08-27 15:13     ` Liliana Marie Prikler
2023-08-27 15:39       ` Hilton Chain via Guix-patches via
2023-08-27 15:49         ` Liliana Marie Prikler
2023-08-28  4:21           ` Hilton Chain via Guix-patches via
2023-08-28 18:28             ` Liliana Marie Prikler
2023-08-29  1:33 ` [bug#65478] [PATCH emacs-team v2] build: emacs-utils: Adjust `emacs-compile-directory' for Emacs 29 Hilton Chain via Guix-patches via
2023-08-30 19:40   ` Liliana Marie Prikler
2023-09-01 16:14     ` Hilton Chain via Guix-patches via
2023-09-01 16:15 ` [bug#65478] [PATCH emacs-team v3] " Hilton Chain via Guix-patches via
2023-09-01 19:37   ` Liliana Marie Prikler
2023-09-09  8:23     ` Liliana Marie Prikler [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=df4f934b7db60fd810b64fc6216c7fdd27b2edb8.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=65478-done@debbugs.gnu.org \
    --cc=andrew@trop.in \
    --cc=hako@ultrarare.space \
    /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.