Re: master cfcf42f 2/2: Ensure that gud commands for non-GDB debuggers are handled by repeat-mode

[Eli Zaretskii]

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>,  juri@linkov.net,
>   leungbk@mailfence.com,  emacs-devel@gnu.org
> Date: Fri, 30 Jul 2021 12:55:29 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > 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).
> 
> It informs about an unfortunate situation that should be fixed (and we
> have indeed fixed them all).  So it's a warning to me.

We cannot do anything with some theses "warnings" shown at bootstrap
time, so how would it be useful to display warnings there?

> > 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.
> 
> On the other hand, my personal advice is to use admin/emake, which
> filters out all the junk so that you don't have to read anything
> carefully.  :-)

I think this is sub-optimal, at least for active developers of Emacs.
No one said a message shown by the build is only important when it's a
warning.