From: Gregory Heytings <gregory@heytings.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: Re: master 5b3c4004a9 2/2: Remove calls to intern with a static string from code that runs on X
Date: Wed, 21 Sep 2022 14:30:11 +0000 [thread overview]
Message-ID: <2d1b683c2280ce5d972e@heytings.org> (raw)
In-Reply-To: <8735clgdat.fsf@yahoo.com>
>
> How about "Try to", dropping "you could" entirely?
>
I'm curious, you seem to dislike the word "you". Why is that? There are
133 occurrences of that word in INSTALL and INSTALL.REPO (together).
>> That would sound like an injunction instead of a suggestion.
>
> Those two are orthogonal, and the advice should be presented rather
> forcefully, since it usually does work.
>
But it's not what everyone who will see that message should do, right?
Emacs developers for example might know why the build is broken and do
something completely different, like fixing a syntax error in some file
and type "make" again. So it shouldn't be, or look like, an injunction,
especially given that two options are presented and we're not suggesting
to try both.
Anyway, I think we've already spent more than enough time on this little
detail. And these messages will possibly be simplified further in the
near future while updating bootstrap-clean.
next prev parent reply other threads:[~2022-09-21 14:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166355307855.3830.3892166668612546304@vcs2.savannah.gnu.org>
[not found] ` <20220919020439.67823C00874@vcs2.savannah.gnu.org>
2022-09-19 6:07 ` master 5b3c4004a9 2/2: Remove calls to intern with a static string from code that runs on X Lars Ingebrigtsen
2022-09-19 6:45 ` Gregory Heytings
2022-09-19 6:53 ` Lars Ingebrigtsen
2022-09-19 7:18 ` Po Lu
2022-09-19 7:42 ` Gregory Heytings
2022-09-19 7:51 ` Po Lu
2022-09-19 7:58 ` Gregory Heytings
2022-09-19 8:01 ` Po Lu
2022-09-19 8:04 ` Gregory Heytings
2022-09-19 8:28 ` Po Lu
2022-09-19 8:32 ` Gregory Heytings
2022-09-20 1:27 ` Po Lu
2022-09-20 7:55 ` Gregory Heytings
2022-09-20 8:17 ` Po Lu
2022-09-20 8:48 ` Gregory Heytings
2022-09-20 11:05 ` Po Lu
2022-09-20 11:24 ` Gregory Heytings
2022-09-20 11:52 ` Po Lu
2022-09-20 12:13 ` Gregory Heytings
2022-09-20 12:46 ` Po Lu
2022-09-20 14:18 ` Gregory Heytings
2022-09-21 2:14 ` Po Lu
2022-09-21 8:39 ` Gregory Heytings
2022-09-21 8:46 ` Emanuel Berg
2022-09-21 10:53 ` Po Lu
2022-09-21 11:01 ` Gregory Heytings
2022-09-21 11:46 ` Po Lu
2022-09-21 14:30 ` Gregory Heytings [this message]
2022-09-22 2:47 ` Po Lu
2022-09-22 5:10 ` Eli Zaretskii
2022-09-20 14:16 ` Eli Zaretskii
2022-09-19 8:27 ` Po Lu
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=2d1b683c2280ce5d972e@heytings.org \
--to=gregory@heytings.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.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).