all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Alan Mackenzie <acm@muc.de>, 31140@debbugs.gnu.org
Subject: bug#31140: Emacs 26, elisp manual, "Syntax Table Internals", a description of flag 'c' is missing.
Date: Fri, 13 Apr 2018 12:36:44 -0400	[thread overview]
Message-ID: <7vh8ofdpwj.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83d0z35efl.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 13 Apr 2018 18:11:42 +0300")

Eli Zaretskii wrote:

>> OK, I've fixed it.  But there must be a time coming, fairly soon, when
>> even doc fixes are no longer welcome.
>
> Why would documentation changes become unwelcome?

They might fail to build in some cases that aren't trivial to spot (eg
with some specific makeinfo version; the manuals being prebuilt in
tarfiles doesn't obviate this because many distributions seem to do
bootstrap builds or builds from git tags); or they might cause problems
with the pdf or html version, which isn't frequently checked. And it
creates work for the person making the release, who can't just release
the release candidate, but has to make another one for frankly trivial
reasons. In short, your interpretation of "release candidate" differs
from mine.





  reply	other threads:[~2018-04-13 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12 19:34 bug#31140: Emacs 26, elisp manual, "Syntax Table Internals", a description of flag 'c' is missing Alan Mackenzie
2018-04-13  7:36 ` Eli Zaretskii
2018-04-13 14:46   ` Alan Mackenzie
2018-04-13 15:11     ` Eli Zaretskii
2018-04-13 16:36       ` Glenn Morris [this message]
2018-04-13 17:45         ` Eli Zaretskii
     [not found] ` <handler.31140.B.1523561775417.ack@debbugs.gnu.org>
2018-04-13 14:50   ` bug#31140: Acknowledgement (Emacs 26, elisp manual, "Syntax Table Internals", a description of flag 'c' is missing.) Alan Mackenzie

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=7vh8ofdpwj.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=31140@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=eliz@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.