From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Po Lu <luangruo@yahoo.com>,
rms@gnu.org, sam@gentoo.org, emacs-devel@gnu.org
Subject: Re: src/Makefile unhelpful
Date: Sun, 11 Sep 2022 14:16:41 +0200 [thread overview]
Message-ID: <877d2ads2e.fsf@gnus.org> (raw)
In-Reply-To: <831qsi9ksq.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 11 Sep 2022 15:07:17 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Maybe _also_ there. But if it's _only_ there, I doubt that people who
> don't know about V=1 will think of looking there.
If somebody is curious about how something is built, they'll look at the
Makefile and they'll look at the README.
Which is why we have lengthy commentary and instructions in the
Makefile. We just don't mention V=1 currently there.
next prev parent reply other threads:[~2022-09-11 12:16 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 2:19 src/Makefile unhelpful Richard Stallman
2022-09-07 2:38 ` Po Lu
2022-09-07 2:41 ` Eli Zaretskii
2022-09-08 3:00 ` Richard Stallman
2022-09-08 4:51 ` Sam James
2022-09-11 3:38 ` Richard Stallman
2022-09-11 5:34 ` Eli Zaretskii
2022-09-11 9:57 ` Lars Ingebrigtsen
2022-09-11 11:59 ` Po Lu
2022-09-11 12:07 ` Eli Zaretskii
2022-09-11 12:16 ` Lars Ingebrigtsen [this message]
2022-09-13 4:07 ` Richard Stallman
2022-09-13 16:11 ` Eli Zaretskii
2022-09-14 20:02 ` Alfred M. Szmidt
2022-09-14 20:05 ` Lars Ingebrigtsen
2022-09-14 20:47 ` Gregory Heytings
2022-09-15 7:14 ` Lars Ingebrigtsen
2022-09-15 7:28 ` Gregory Heytings
2022-09-15 7:32 ` Eli Zaretskii
2022-09-15 7:41 ` Gregory Heytings
2022-09-15 9:07 ` Eli Zaretskii
2022-09-15 14:33 ` Óscar Fuentes
2022-09-15 16:04 ` Gregory Heytings
2022-09-17 10:46 ` Gregory Heytings
2022-09-17 11:20 ` Alan Mackenzie
2022-09-17 16:41 ` Michael Welsh Duggan
2022-09-17 22:59 ` Gregory Heytings
2022-09-17 22:58 ` Gregory Heytings
2022-09-18 10:37 ` Lars Ingebrigtsen
2022-09-18 11:38 ` Gerd Möllmann
2022-09-18 11:53 ` Andreas Schwab
2022-09-18 12:05 ` Gerd Möllmann
2022-09-18 13:48 ` Robert Pluim
2022-09-18 16:40 ` Gregory Heytings
2022-09-18 16:59 ` Andreas Schwab
2022-09-18 21:50 ` Gregory Heytings
2022-09-19 17:20 ` chad
2022-09-19 17:25 ` Eli Zaretskii
2022-09-19 20:42 ` Stefan Monnier
2022-09-18 21:39 ` Gregory Heytings
2022-09-15 13:13 ` Ken Brown
2022-09-15 14:01 ` Gregory Heytings
2022-09-11 15:16 ` Werner LEMBERG
2022-09-12 4:35 ` Richard Stallman
2022-09-08 6:14 ` Eli Zaretskii
2022-09-08 7:29 ` Andreas Schwab
2022-09-08 13:18 ` Stefan Monnier
2022-09-11 3:38 ` Richard Stallman
2022-09-11 5:42 ` Eli Zaretskii
2022-09-14 4:12 ` Richard Stallman
2022-09-14 11:33 ` Eli Zaretskii
2022-09-07 3:11 ` Sam James
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=877d2ads2e.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=rms@gnu.org \
--cc=sam@gentoo.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).