From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: [ELPA] Package proposal: relint (ex-trawl)
Date: Wed, 20 Mar 2019 09:08:17 -0400 [thread overview]
Message-ID: <jwvwoktpugn.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 83d0mmt7mf.fsf@gnu.org
> My point is that "make check" is supposed to be an integral part of
> any serious build of a program, including Emacs. Whenever I build
> Emacs for the first time on some machine, I always run the test suite.
I don't think relint should be part of `make check` since its purpose is
very different (it doesn't try to verify the functional correctness of
the code by running it).
It should be a separate `make relint`.
You use `make check` above as a way to (try to) ensure that a build is
functional, and running relint will not help with that since it only
looks at the source code and not the resulting behavior.
Stefan
next prev parent reply other threads:[~2019-03-20 13:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 13:24 [ELPA] Package proposal: relint (ex-trawl) Mattias Engdegård
2019-03-19 18:05 ` Eli Zaretskii
2019-03-19 20:30 ` Mattias Engdegård
2019-03-19 21:43 ` Stefan Monnier
2019-03-20 5:52 ` Eli Zaretskii
2019-03-20 13:08 ` Stefan Monnier [this message]
2019-03-20 13:25 ` Eli Zaretskii
2019-03-21 11:19 ` Mattias Engdegård
2019-03-21 14:26 ` Eli Zaretskii
2019-03-22 14:17 ` Mattias Engdegård
2019-03-22 14:31 ` Stefan Monnier
2019-03-22 14:49 ` Eli Zaretskii
2019-03-22 15:01 ` Stefan Monnier
2019-03-22 15:20 ` Eli Zaretskii
2019-03-22 15:49 ` Stefan Monnier
2019-03-22 16:12 ` Stefan Monnier
2019-03-22 18:18 ` Stefan Monnier
2019-03-22 18:36 ` T.V Raman
2019-03-23 2:33 ` Richard Stallman
2019-03-26 14:14 ` Mattias Engdegård
2019-03-26 16:00 ` Eli Zaretskii
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=jwvwoktpugn.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.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.
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).