unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca,
	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 13:16:10 +0200	[thread overview]
Message-ID: <87a6m4qcg5.fsf@gnus.org> (raw)
In-Reply-To: <83o8akqd0u.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 30 Jul 2021 14:03:45 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

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

I don't get any warnings when saying "make bootstrap"?  Which ones are
you referring to?

>> 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.

emake doesn't filter out everything that's a not a warning, so I don't
follow you here.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2021-07-30 11:16 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
2021-07-30 10:55               ` Lars Ingebrigtsen
2021-07-30 11:03                 ` Eli Zaretskii
2021-07-30 11:16                   ` Lars Ingebrigtsen [this message]
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

  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=87a6m4qcg5.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --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 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).