all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 68083@debbugs.gnu.org, acorallo@gnu.org, jschmidt4gnu@vodafonemail.de
Subject: bug#68083: 30.0.50; Intermittent build failure with native compilation
Date: Sun, 31 Dec 2023 08:26:43 +0200	[thread overview]
Message-ID: <83wmsu3n18.fsf@gnu.org> (raw)
In-Reply-To: <CAHyO48wX+hyERCt7Py3xyT-dQFvtzAh4i5Bk8-uOJBGjWo3P+g@mail.gmail.com> (message from Aaron Jensen on Sat, 30 Dec 2023 14:54:53 -0600)

> From: Aaron Jensen <aaronjensen@gmail.com>
> Date: Sat, 30 Dec 2023 14:54:53 -0600
> Cc: Andrea Corallo <acorallo@gnu.org>, 68083@debbugs.gnu.org, 
> 	Jens Schmidt <jschmidt4gnu@vodafonemail.de>
> 
> Works for me, though is it still an outstanding question as to whether or not we should add macro
> expand back?

Andrea, WDYT?





  parent reply	other threads:[~2023-12-31  6:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-28 14:05 bug#68083: 30.0.50; Intermittent build failure with native compilation Aaron Jensen
2023-12-28 15:12 ` Eli Zaretskii
2023-12-29 18:43   ` Andrea Corallo
2023-12-29 19:09     ` Aaron Jensen
2023-12-29 20:17       ` Andrea Corallo
2023-12-29 20:26         ` Aaron Jensen
2023-12-29 21:07           ` Aaron Jensen
2023-12-30  6:47             ` Eli Zaretskii
2023-12-30 15:29               ` Aaron Jensen
2023-12-30 17:42                 ` Eli Zaretskii
2023-12-30 18:06                   ` Aaron Jensen
2023-12-30 18:46                     ` Eli Zaretskii
2023-12-30 20:54                       ` Aaron Jensen
2023-12-30 23:08                         ` Aaron Jensen
2023-12-31  6:26                         ` Eli Zaretskii [this message]
2024-01-01 19:39                           ` Andrea Corallo
2024-01-01 20:12                             ` Eli Zaretskii
2023-12-31 20:30         ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=83wmsu3n18.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=68083@debbugs.gnu.org \
    --cc=aaronjensen@gmail.com \
    --cc=acorallo@gnu.org \
    --cc=jschmidt4gnu@vodafonemail.de \
    /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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.