From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 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 20:45:44 +0300 [thread overview]
Message-ID: <837epb57av.fsf@gnu.org> (raw)
In-Reply-To: <7vh8ofdpwj.fsf@fencepost.gnu.org> (message from Glenn Morris on Fri, 13 Apr 2018 12:36:44 -0400)
> From: Glenn Morris <rgm@gnu.org>
> Cc: Alan Mackenzie <acm@muc.de>, 31140@debbugs.gnu.org
> Date: Fri, 13 Apr 2018 12:36:44 -0400
>
> 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.
With such simple changes, this is unlikely.
> 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.
That ship has sailed already, because we have one code change on the
release branch which I considered important enough to have.
> In short, your interpretation of "release candidate" differs from
> mine.
We've established that already during the previous release, I don't
see why you needed to reiterate that. But feel free to volunteer to
be the next maintainer, I will gladly step down that very moment,
because I think you are a much better candidate for that job.
next prev parent reply other threads:[~2018-04-13 17:45 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
2018-04-13 17:45 ` Eli Zaretskii [this message]
[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
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=837epb57av.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31140@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=rgm@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 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).