From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, leungbk@mailfence.com, juri@linkov.net
Subject: Re: master cfcf42f 2/2: Ensure that gud commands for non-GDB debuggers are handled by repeat-mode
Date: Fri, 30 Jul 2021 08:43:12 +0300 [thread overview]
Message-ID: <837dh8s6fj.fsf@gnu.org> (raw)
In-Reply-To: <87zgu4ri8b.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 29 Jul 2021 22:13:40 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Thu, 29 Jul 2021 22:13:40 +0200
> Cc: Brian Leung <leungbk@mailfence.com>, emacs-devel@gnu.org
>
> Juri Linkov <juri@linkov.net> writes:
>
> >> Yeah, the warning should probably be rewritten to start with "Warning: "
> >> or something?
> >
> > It's displayed as a warning only when prefixed with "0:0:0: Warning: ".
>
> Right, so we could change this message to say that?
I'm not sure it's a warning. It's an informative message, and some of
them are always displayed during bootstrap. Making them warnings
would then apply pressure on us to remove them, which we cannot easily
do in the case of those other messages (unlike the one caused by the
changeset in this bug).
Stefan, any comments/suggestions?
My personal advice is to read carefully every line displayed by the
build process, and not limit yourself to warnings. Messages that
aren't supposed to appear during a normal build should be discovered
regardless of whether they are warnings/errors or not.
next prev parent reply other threads:[~2021-07-30 5:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210727211521.15408.98852@vcs0.savannah.gnu.org>
[not found] ` <20210727211523.AE6F72065F@vcs0.savannah.gnu.org>
2021-07-28 15:40 ` master cfcf42f 2/2: Ensure that gud commands for non-GDB debuggers are handled by repeat-mode Lars Ingebrigtsen
2021-07-28 16:24 ` Juri Linkov
2021-07-28 16:35 ` Lars Ingebrigtsen
2021-07-28 16:49 ` Juri Linkov
2021-07-29 20:13 ` Lars Ingebrigtsen
2021-07-29 22:43 ` Juri Linkov
2021-07-30 10:53 ` Lars Ingebrigtsen
2021-07-30 17:51 ` Juri Linkov
2021-07-30 18:13 ` Lars Ingebrigtsen
2021-07-30 5:43 ` Eli Zaretskii [this message]
2021-07-30 10:55 ` Lars Ingebrigtsen
2021-07-30 11:03 ` Eli Zaretskii
2021-07-30 11:16 ` Lars Ingebrigtsen
2021-07-30 12:13 ` Eli Zaretskii
2021-07-30 12:20 ` Lars Ingebrigtsen
2021-07-30 13:22 ` Eli Zaretskii
2021-07-30 14:39 ` Lars Ingebrigtsen
2021-07-30 17:54 ` Juri Linkov
2021-07-30 18:26 ` Eli Zaretskii
2021-07-30 22:08 ` Stefan Monnier
2021-07-30 22:03 ` Stefan Monnier
2021-08-01 8:32 ` Juri Linkov
2021-08-01 10:42 ` Lars Ingebrigtsen
2021-08-01 14: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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837dh8s6fj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=leungbk@mailfence.com \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.