From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: kcbanner@gmail.com, 73159@debbugs.gnu.org
Subject: bug#73159: exec/configure.ac
Date: Tue, 10 Sep 2024 15:41:03 +0300 [thread overview]
Message-ID: <865xr3vfz4.fsf@gnu.org> (raw)
In-Reply-To: <875xr3rh54.fsf@yahoo.com> (bug-gnu-emacs@gnu.org)
> Cc: 73159@debbugs.gnu.org
> Date: Tue, 10 Sep 2024 17:29:27 +0800
> From: Po Lu via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> Casey Banner <kcbanner@gmail.com> writes:
>
> > AC_INIT([libexec], [30.0.50], [bug-gnu-emacs@gnu.org], [],
> > [https://www.gnu.org/software/emacs/])
>
> This version number shouldn't appear in any binaries built for
> MS-Windows (or otherwise than for Android in general), and its value is
> not really significant even there.
Unrelated to the problem of the MinGW build, the fact that
exec/configure.ac is not modified by admin/admin.el:set-version is a
bug, don't you agree? We should have 30.0.90 in that file, not
30.0.50, right?
next prev parent reply other threads:[~2024-09-10 12:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 4:15 bug#73159: 30.0.90; uniscribe / harfbuzz are not initialized on Windows, resulting in fallback to gdi Casey Banner
2024-09-10 5:50 ` bug#73159: Casey Banner
2024-09-10 9:29 ` bug#73159: Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-10 12:41 ` Eli Zaretskii [this message]
2024-09-10 13:08 ` bug#73159: exec/configure.ac Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-10 12:33 ` bug#73159: 30.0.90; uniscribe / harfbuzz are not initialized on Windows, resulting in fallback to gdi Eli Zaretskii
2024-09-10 18:31 ` Casey Banner
2024-09-10 18:47 ` Eli Zaretskii
[not found] ` <CAKHgf3AXx1F0oUU5UJZJOo9GfieEJTuHRx14oqwH+bsoiKtW7A@mail.gmail.com>
2024-09-10 18:56 ` bug#73159: Fwd: " Casey Banner
2024-09-11 2:25 ` Eli Zaretskii
2024-09-10 12:20 ` 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=865xr3vfz4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73159@debbugs.gnu.org \
--cc=kcbanner@gmail.com \
--cc=luangruo@yahoo.com \
/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).