unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: 23611@debbugs.gnu.org
Subject: bug#23611: generating pdf manuals fails with TeX capacity exceeded
Date: Wed, 25 May 2016 15:51:16 -0700	[thread overview]
Message-ID: <7ea17c5e-b563-df10-68d3-15c1fea1cde7@cs.ucla.edu> (raw)
In-Reply-To: <65eg8q3rec.fsf@fencepost.gnu.org>

On 05/25/2016 11:48 AM, Glenn Morris wrote:
> It is a (totally opaque, for me at least) change to the mechanism that
> generates documentation

Sure, but it affects only documentation, which was (and still is) 
generally fair game for the emacs-25 branch. Equivalence of code and 
data, and all that.

Generally speaking, changes to Gnulib-derived files should follow the 
same rules that we use for changes to other files. For example, I 
stopped copying .c files from Gnulib when the pretest became closed to 
all code changes other than fixes to blocking bugs, because the Gnulib 
changes since then have not fixed blocking bugs.






  reply	other threads:[~2016-05-25 22:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24 17:38 bug#23611: generating pdf manuals fails with TeX capacity exceeded Glenn Morris
2016-05-25 16:53 ` Eli Zaretskii
2016-05-25 17:45 ` Paul Eggert
2016-05-25 18:48   ` Glenn Morris
2016-05-25 22:51     ` Paul Eggert [this message]
2016-05-25 19:30   ` Eli Zaretskii
2016-05-25 18:08 ` bug#23611: texinfo.tex 2016-05-07.20: "Tex capacity exceeded" with Emacs manuals Paul Eggert

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=7ea17c5e-b563-df10-68d3-15c1fea1cde7@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=23611@debbugs.gnu.org \
    --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).