unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: info files
Date: Tue, 24 Dec 2013 15:32:12 +0900	[thread overview]
Message-ID: <87zjnqn4ib.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <52B92093.3030908@cs.ucla.edu>

Paul Eggert writes:

 > The GNU coding standards says that 'make all' need not
 > rebuild documentation files,

Then the coding standards are buggy! ;-)

Seriously, having "make" rebuild docs doesn't *violate* the standard,
does it?  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", and in any other situation
.texi files change far less frequently than C or Lisp source, and
rebuild quickly (except maybe the Lispref).








  reply	other threads:[~2013-12-24  6:32 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 [this message]
2013-12-24 18:02       ` Paul Eggert
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=87zjnqn4ib.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@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).