From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org, karl@freefriends.org
Subject: Re: makeinfo 4.7
Date: Mon, 28 Aug 2006 10:20:36 +0200 [thread overview]
Message-ID: <m3sljhe0ff.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1GHTFy-0000sD-4E@fencepost.gnu.org> (Eli Zaretskii's message of "Sun, 27 Aug 2006 18:37:30 -0400")
Eli Zaretskii <eliz@gnu.org> writes:
> If it is really necessary to ask them to upgrade, I agree. But this
> is not our case. Are you saying we should ask people to upgrade for
> no good reason at all?
When I started (again) to hack on CVS emacs years ago, I also had to
upgrade makeinfo (to 4.3 at that time). Now, years later, I had
to upgrade to makeinfo 4.8. Fine! It took just 10 minutes.
Just like we prefer that users upgrade to the latest version of emacs
(to avoid spending time on bug reports for older versions), I'm sure
the maintainers of makeinfo also prefer people to use the latest
version.
So why should emacs (of all projects) not use an up-to-date version of
makeinfo? I don't see the problem at all.
Still, wasn't there a time where the make process would barf with
an error message telling what version of makeinfo was required if
the installed version is too old???
BTW, isn't it about time [after the release] to get rid of the P_
macro, and assume that all systems have an ANSI-C complient compiler
these days?
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2006-08-28 8:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 21:54 makeinfo 4.7 Kim F. Storm
2006-08-25 23:03 ` Eli Zaretskii
2006-08-25 23:35 ` Kim F. Storm
2006-08-26 8:11 ` Alan Mackenzie
2006-08-26 12:15 ` Eli Zaretskii
2006-08-26 12:46 ` Eli Zaretskii
2006-08-26 14:23 ` Alan Mackenzie
2006-09-01 17:55 ` Eli Zaretskii
2006-08-26 12:22 ` Richard Stallman
2006-08-26 17:11 ` Karl Berry
2006-08-27 14:34 ` Richard Stallman
2006-08-27 16:16 ` Eli Zaretskii
2006-08-27 16:26 ` David Kastrup
2006-08-27 22:27 ` Eli Zaretskii
2006-08-27 22:30 ` David Kastrup
2006-08-27 22:37 ` Eli Zaretskii
2006-08-27 23:03 ` David Kastrup
2006-08-30 9:48 ` Eli Zaretskii
2006-08-30 9:52 ` David Kastrup
2006-08-28 8:20 ` Kim F. Storm [this message]
2006-08-29 16:06 ` Karl Berry
2006-08-29 16:49 ` Stefan Monnier
2006-08-30 11:27 ` Eli Zaretskii
2006-08-30 13:34 ` Kim F. Storm
2006-08-30 9:57 ` Eli Zaretskii
2006-08-30 11:20 ` Kim F. Storm
2006-08-30 22:59 ` Juri Linkov
2006-08-30 23:33 ` David Kastrup
2006-08-31 2:42 ` Miles Bader
2006-08-31 3:30 ` Eli Zaretskii
2006-08-31 23:35 ` Juri Linkov
2006-08-28 22:09 ` Richard Stallman
2006-08-30 10:44 ` Eli Zaretskii
2006-09-01 17:53 ` Eli Zaretskii
2006-08-28 15:14 ` Stefan Monnier
2006-08-30 10:32 ` 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=m3sljhe0ff.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=karl@freefriends.org \
/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).