From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.6-97-ge8772a9
Date: Fri, 30 Nov 2012 21:18:08 +0100 [thread overview]
Message-ID: <877gp2975r.fsf@gnu.org> (raw)
In-Reply-To: <871ufax5tq.fsf@tines.lan> (Mark H. Weaver's message of "Fri, 30 Nov 2012 14:13:05 -0500")
Hi,
Mark H Weaver <mhw@netris.org> skribis:
> Sorry for not noticing this earlier, but I should mention that although
> I use some of the warnings infrastructure for reporting the
> 'duplicate-case-datum' and 'bad-case-datum' warnings, I never check for
> those warning flags. The warnings are reported unconditionally.
Oops, I had overlooked that.
> I had started to work on a patch set to make them conditional, but that
> work was halted due to an unresolved disagreement about how warnings
> should be specified.
>
> http://lists.gnu.org/archive/html/guile-devel/2012-02/msg00080.html
As an aside, it’s really hard for me to deal with work that’s “halted”.
I’d rather resolve them quickly, than just let them be forgotten, and
eventually revive them.
> I felt, and continue to strongly feel, that we should not require the
> user to provide a complete list of warning types that they want. If we
> do that, then users will be forced to hard-code that list into their
> build systems (and/or code that uses 'compile'). If they do this, then
> whenever we add a new warning type, no one will see the new warnings
> until they modify their build system.
>
> Can we revisit this issue?
Sure. Can you reply to my last message in the thread? :-)
Thanks,
Ludo’.
prev parent reply other threads:[~2012-11-30 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Tc2bi-0001Rw-2W@vcs.savannah.gnu.org>
2012-11-30 19:13 ` [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.6-97-ge8772a9 Mark H Weaver
2012-11-30 20:18 ` Ludovic Courtès [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877gp2975r.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.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).