From: Lars Ingebrigtsen <larsi@gnus.org>
To: Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>
Cc: Po Lu <luangruo@yahoo.com>,
"H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>,
worik <root@worik.org>,
53627@debbugs.gnu.org
Subject: bug#53627: 29.0.50; Incorrect installation instructions
Date: Mon, 31 Jan 2022 16:25:10 +0100 [thread overview]
Message-ID: <87fsp42ai1.fsf@gnus.org> (raw)
In-Reply-To: <87ee4org12.fsf@turtle-trading.net> (Benjamin Riefenstahl's message of "Sun, 30 Jan 2022 23:54:17 +0100")
Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net> writes:
>> INSTALL and README are intended for the vast majority of people who
>> download the release off ftp.gnu.org (or alpha.gnu.org for pretests.)
>
> I'm not sure this is true anymore. I'm guessing these days most people
> use pre-built binaries, and those who do get the source get it straight
> from the Git instead of the tarballs. Maybe that note that if you clone
> the repo you should look at INSTALL.REPO could be more prominent in
> INSTALL? When Dieter quoted the paragraph from INSTALL above, I could
> not even find that note at first glance, even though I knew what must be
> in there.
I didn't see it either. I've now made it into a separate paragraph, and
made it slightly less obscure.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-01-31 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 21:39 bug#53627: 29.0.50; Incorrect installation instructions worik
2022-01-29 21:48 ` H. Dieter Wilhelm
2022-01-29 21:52 ` worik
2022-01-29 22:05 ` H. Dieter Wilhelm
2022-01-30 6:27 ` Eli Zaretskii
2022-01-30 1:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-30 22:54 ` Benjamin Riefenstahl
2022-01-31 15:25 ` Lars Ingebrigtsen [this message]
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=87fsp42ai1.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=53627@debbugs.gnu.org \
--cc=b.riefenstahl@turtle-trading.net \
--cc=dieter@duenenhof-wilhelm.de \
--cc=luangruo@yahoo.com \
--cc=root@worik.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).