From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bzg@altern.org, emacs-devel@gnu.org
Subject: Re: /srv/bzr/emacs/trunk r111840: Port documentation to Texinfo 5.0.
Date: Thu, 21 Feb 2013 20:35:45 +0200 [thread overview]
Message-ID: <83y5ehms5a.fsf@gnu.org> (raw)
In-Reply-To: <51265ACA.9000706@cs.ucla.edu>
> Date: Thu, 21 Feb 2013 09:35:06 -0800
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: Bastien <bzg@altern.org>, emacs-devel@gnu.org
>
> By the way, Texinfo 5.0 is *way* slower, so you probably don't want
> to upgrade Texinfo unless you've got a fast machine. On my last-year's
> desktop (AMD Phenom II X4 910e) it takes over 3 minutes of CPU time
> to make Emacs's info files.
It took 5 minutes on a Core Duo, and 3 min on a Core i7 (vs 6 sec with
makeinfo 4.13).
> See the thread starting at
> <http://lists.gnu.org/archive/html/bug-texinfo/2013-02/msg00049.html>.
Very sad.
I keep the v4.13a makeinfo around (and renamed the v5.0 to
'makeinfo5').
Btw, I think this fixing of the manuals should have been done on the
release branch, because users _will_ try building the manuals with
Texinfo 5 when Emacs 24.3 is released.
next prev parent reply other threads:[~2013-02-21 18:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1U8Mer-0006Zn-J7@vcs.savannah.gnu.org>
2013-02-21 8:14 ` /srv/bzr/emacs/trunk r111840: Port documentation to Texinfo 5.0 Bastien
2013-02-21 17:25 ` Eli Zaretskii
2013-02-21 17:35 ` Paul Eggert
2013-02-21 18:35 ` Eli Zaretskii [this message]
2013-02-21 19:03 ` Glenn Morris
2013-02-21 21:35 ` Paul Eggert
2013-02-22 19:16 ` Eli Zaretskii
2013-02-22 19:29 ` Glenn Morris
2013-02-22 20:12 ` Eli Zaretskii
2013-02-22 20:34 ` Michael Albinus
2013-02-22 20:50 ` Eli Zaretskii
2013-02-24 18:21 ` Michael Albinus
2013-02-24 19:25 ` Glenn Morris
2013-02-24 20:13 ` Michael Albinus
2013-02-24 21:02 ` Eli Zaretskii
2013-02-25 8:33 ` Michael Albinus
2013-02-24 21:01 ` Eli Zaretskii
2013-02-21 19:14 ` Michael Albinus
2013-02-21 21:56 ` Bastien
2013-02-21 21:58 ` Bastien
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=83y5ehms5a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bzg@altern.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.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 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.