From: Paul Eggert <eggert@cs.ucla.edu>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacs-devel@gnu.org
Subject: Re: info files
Date: Tue, 24 Dec 2013 10:02:22 -0800 [thread overview]
Message-ID: <52B9CC2E.80202@cs.ucla.edu> (raw)
In-Reply-To: <87zjnqn4ib.fsf@uwakimon.sk.tsukuba.ac.jp>
Stephen J. Turnbull wrote:
> having "make" rebuild docs doesn't *violate* the standard,
> does it?
True.
> AFAICS, it would be a one-time annoyance per existing
> checkout: the first time you rebuild after the commit of "bzr rm
> info", it would take a noticable amount of time. But surely it's
> hardly noticable in a "make bootstrap".
It takes quite some time even compared to a "make bootstrap",
I'm afraid. On my platform (AMD Phenom II X4 910e, texinfo 5.2),
a fresh "make info" takes 3 minutes 19 seconds. It can be parallelized with "make -j",
but some developers are still using older single-core machines,
considerably slower than what I use.
Plus, one doesn't need to run "make bootstrap" from a fresh checkout.
next prev parent reply other threads:[~2013-12-24 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 16:07 info files Stephen Berman
2013-12-23 17:10 ` Andreas Schwab
2013-12-23 17:17 ` Stephen Berman
2013-12-24 2:30 ` Stephen J. Turnbull
2013-12-24 5:50 ` Paul Eggert
2013-12-24 6:32 ` Stephen J. Turnbull
2013-12-24 18:02 ` Paul Eggert [this message]
2013-12-24 18:14 ` Eli Zaretskii
2013-12-24 18:27 ` Lars Ingebrigtsen
2013-12-24 18:37 ` Lars Ingebrigtsen
2013-12-24 18:52 ` Eli Zaretskii
2013-12-24 19:28 ` Stefan Monnier
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=52B9CC2E.80202@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.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).