From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: tbading@web.de, acm@muc.de, emacs-devel@gnu.org
Subject: Re: Org mode update breaking build?
Date: Thu, 04 May 2023 08:48:01 +0300 [thread overview]
Message-ID: <83cz3glka6.fsf@gnu.org> (raw)
In-Reply-To: <s8h4josemhn.fsf@yahoo.com> (message from Po Lu on Thu, 04 May 2023 12:42:12 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: Tobias Bading <tbading@web.de>, acm@muc.de, emacs-devel@gnu.org
> Date: Thu, 04 May 2023 12:42:12 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > We already fixed that, but only on master. So you don't need to
> > convince anyone that this needed fixing. We are convinced.
>
> Is there any reason Org Mode needs to signal a compilation error in this
> case?
It no longer does, on master.
Please read the thread if you want to know the gory details, I'd
rather we didn't repeat all that.
> And if there is, why not simply make all the Org elc files depend on
> each other in deps.mk or something?
Because it's impractical (too many files, some of which may not exist
or be outdated etc.), and because it doesn't really work in this case.
I tried that as the first attempt at solving the problem.
next prev parent reply other threads:[~2023-05-04 5:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 15:26 Org mode update breaking build? Tobias Bading
2023-05-03 15:55 ` Alan Mackenzie
2023-05-03 16:11 ` Tobias Bading
2023-05-03 16:58 ` Eli Zaretskii
2023-05-03 17:02 ` Tobias Bading
2023-05-04 4:42 ` Po Lu
2023-05-04 5:48 ` Eli Zaretskii [this message]
2023-05-09 16:34 ` Sam Steingold
2023-05-09 16:47 ` Eli Zaretskii
2023-05-09 17:17 ` Sam Steingold
2023-05-09 19:07 ` Eli Zaretskii
2023-05-10 18:12 ` Sam Steingold
2023-05-08 12:00 ` Madhu
2023-05-08 13:22 ` Eli Zaretskii
2023-05-14 5:49 ` Madhu
2023-05-14 5:59 ` Eli Zaretskii
2023-05-03 16:04 ` Eli Zaretskii
2023-05-03 16:07 ` Tobias Bading
2023-05-03 16:57 ` Eli Zaretskii
2023-05-03 18:56 ` John ff
2023-05-03 19:02 ` Tassilo Horn
2023-05-04 2:00 ` Michael Heerdegen
2023-05-04 3:23 ` Bob Rogers
2023-05-04 3:30 ` Michael Heerdegen
2023-05-04 3:44 ` Bob Rogers
2023-05-04 5:42 ` Eli Zaretskii
2023-05-04 5:58 ` Bob Rogers
2023-05-04 5:41 ` Eli Zaretskii
2023-05-04 5:13 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83cz3glka6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=tbading@web.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).