From: Luc Teirlinck <teirllm@dms.auburn.edu>
Subject: Recent problems with `make bootstrap'.
Date: Wed, 8 Dec 2004 22:19:34 -0600 (CST) [thread overview]
Message-ID: <200412090419.iB94JYd16562@raven.dms.auburn.edu> (raw)
Due to a recent change in the bootstrapping process, bootstrapping no
longer fails, but proceeds as usual, if one of the manuals fails to
build, without any noticeable warning to the user. The Elisp manual
no longer builds, and the breaking of the build is deliberate. It is
trivial to fix. As a result, people are reading and checking an
outdated version of the manual and submitting bug reports and comments
about the outdated version.
Before, if a manual failed to build, it immediately got detected and
fixed in a matter of hours. Building manuals gets broken rather
frequently through all kinds of typos or stupid inadvertent omissions.
So the Emacs manual or info.texi could start failing to build and no
longer get updated at any time without anybody noticing.
This wastes the time of people who volunteer time to check the manuals
and seriously interferes with the checking of the manuals. This
apparent lack of concern for people's time is discouraging.
Why not revert Revision 1.299 to Makefile.in and get rid of these two
xref's pointing nowhere and quit wasting people's time? I have had to
do that in my private version of Emacs, since otherwise checking the
manuals would be hopeless.
I do not "morally disapprove" of xref's pointing nowhere, but I can
not see how they are an important feature. They are not "wrong", just
useless. We _are_ going to remember about those two variables.
Sincerely,
Luc.
next reply other threads:[~2004-12-09 4:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 4:19 Luc Teirlinck [this message]
2004-12-09 11:38 ` Recent problems with `make bootstrap' Han Boetes
2004-12-09 14:53 ` Luc Teirlinck
2004-12-09 16:18 ` Thien-Thi Nguyen
2004-12-09 18:29 ` David Kastrup
2004-12-09 20:47 ` Thien-Thi Nguyen
2004-12-09 18:35 ` Luc Teirlinck
2004-12-09 21:12 ` Thien-Thi Nguyen
2004-12-10 11:05 ` 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=200412090419.iB94JYd16562@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
/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).