From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: contovob@tcd.ie, rgm@gnu.org, 45143@debbugs.gnu.org
Subject: bug#45143: Missing source for some doc/misc manuals (moral-issue)
Date: Wed, 17 Feb 2021 19:28:13 +0200 [thread overview]
Message-ID: <83a6s27geq.fsf@gnu.org> (raw)
In-Reply-To: <877dn6ekld.fsf@gmail.com> (message from Robert Pluim on Wed, 17 Feb 2021 17:15:58 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: contovob@tcd.ie, rgm@gnu.org, 45143@debbugs.gnu.org
> Date: Wed, 17 Feb 2021 17:15:58 +0100
>
> Eli> Not necessarily. having the instructions in the README should be
> Eli> enough. (Making Info from .org as part of the build could be
> Eli> problematic, since we need a functional Emacs for that. While that
> Eli> could be done, I don't see why we should bother.)
>
> We need a functional emacs to byte-compile files as well, I donʼt see
> why this is any different.
It's a complication, since we generally build the manuals right at the
beginning.
> In my mind, source code without the accompanying build instructions is
> incomplete (unless you count the README as those instructions).
I do count README as instructions for this purpose.
next prev parent reply other threads:[~2021-02-17 17:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 17:41 bug#45143: Missing source for some doc/misc manuals? Glenn Morris
2020-12-15 18:17 ` Glenn Morris
2021-01-31 21:47 ` Glenn Morris
2021-02-17 5:40 ` bug#45143: Missing source for some doc/misc manuals (moral-issue) Glenn Morris
2021-02-17 8:45 ` Robert Pluim
2021-02-17 14:27 ` Basil L. Contovounesios
2021-02-17 14:41 ` Robert Pluim
2021-02-17 16:09 ` Eli Zaretskii
2021-02-17 16:15 ` Robert Pluim
2021-02-17 17:28 ` Eli Zaretskii [this message]
2021-02-19 5:34 ` Richard Stallman
2021-02-19 5:57 ` Glenn Morris
2021-02-21 6:15 ` Richard Stallman
2021-02-21 6:15 ` bug#45143: Incorrect markup in some doc/misc manuals Richard Stallman
2021-02-21 11:01 ` Protesilaos Stavrou
2021-02-22 6:22 ` Richard Stallman
2021-02-22 16:38 ` Protesilaos Stavrou
2021-02-24 7:38 ` Protesilaos Stavrou
2021-02-24 15:13 ` Eli Zaretskii
2021-02-25 6:04 ` Protesilaos Stavrou
2021-02-25 14:40 ` Eli Zaretskii
2021-02-27 3:49 ` Glenn Morris
2021-02-27 3:55 ` Glenn Morris
2021-02-27 6:29 ` Protesilaos Stavrou
2021-02-21 20:11 ` Eli Zaretskii
2021-02-24 6:49 ` Richard Stallman
2021-02-24 15:09 ` Eli Zaretskii
2021-02-26 6:32 ` Richard Stallman
2021-02-26 7:45 ` Eli Zaretskii
2021-02-27 16:14 ` Richard Stallman
2021-02-27 18:20 ` Eli Zaretskii
2021-03-01 5:18 ` Richard Stallman
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=83a6s27geq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45143@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=rgm@gnu.org \
--cc=rpluim@gmail.com \
/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).