From: Per Bothner <per@bothner.com>
To: Duncan Mak <duncanmak@gmail.com>
Cc: kawa mailing list <kawa@sourceware.org>
Subject: Re: Show all warnings and errors
Date: Mon, 19 Sep 2022 12:48:40 +0200 [thread overview]
Message-ID: <126f7ad3-285e-7453-2f1e-f07064c294d7@bothner.com> (raw)
In-Reply-To: <CABgWrqons2pBJdGJovZ2SJzH8hejucRjRM88L8-9Lk7s98XLEw@mail.gmail.com>
On 9/19/22 15:06, Duncan Mak wrote:
> Thanks for the idea, i made a merge request here:
>
> Use Compilation.maxErrors instead of a hardcoded constant (!37) · Merge requests · kashell / Kawa · GitLab <https://gitlab.com/kashell/Kawa/-/merge_requests/37>
>
> With this patch, I can see all the errors now, thanks!
Merged - thanks!
--
--Per Bothner
per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2022-09-19 10:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 23:18 Duncan Mak
2019-01-01 2:12 ` Per Bothner
2019-01-01 2:33 ` Duncan Mak
2019-01-01 2:42 ` Per Bothner
2019-01-01 20:47 ` Duncan Mak
2019-01-01 20:58 ` Per Bothner
2019-01-01 21:16 ` Duncan Mak
2019-01-01 21:24 ` Per Bothner
2019-01-01 21:31 ` Duncan Mak
2019-01-01 21:42 ` Per Bothner
2019-01-01 22:08 ` Duncan Mak
2022-09-18 3:03 ` Duncan Mak
2022-09-18 19:11 ` Per Bothner
2022-09-18 22:06 ` Duncan Mak
2022-09-19 10:48 ` Per Bothner [this message]
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=126f7ad3-285e-7453-2f1e-f07064c294d7@bothner.com \
--to=per@bothner.com \
--cc=duncanmak@gmail.com \
--cc=kawa@sourceware.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.
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).