From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: emacs-pretest-bug@gnu.org, Luc Teirlinck <teirllm@dms.auburn.edu>,
ding@gnus.org
Subject: Re: Change in bytecomp.el breaks Gnus
Date: Sun, 14 Nov 2004 22:44:26 +0900 [thread overview]
Message-ID: <yotl4qjs5yv9.fsf@jpl.org> (raw)
In-Reply-To: <m1y8h5vsy6.fsf-monnier+emacs@gnu.org>
>>>>> In <m1y8h5vsy6.fsf-monnier+emacs@gnu.org>
>>>>> Stefan <monnier@iro.umontreal.ca> wrote:
> I'm not sure you realize that my code is not just shorter but it gets you
> rid of the warning (if you use a recent enough version of Emacs-CVS).
Yes, I know we get a lot of warnings to Gnus modules while
bootstrapping Emacs CVS. Even though there's a serious problem,
it will be buried into them. OTOH, Gnus CVS filters those
negligible warnings carefully using dgnushack.el and lpath.el.
It is useful to finding something wrong when performing `make'.
>>> (defalias 'foo
>>> (if (fboundp 'message) 'message 'ignore))
>> That's okay.
That I wrote `okay' means that we will have to modify them in
Gnus if it is really necessity (i.e., the case where it is
unable to silence bytecomp).
next prev parent reply other threads:[~2004-11-14 13:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877jouepy8.fsf@telia.com>
[not found] ` <b9yd5ymkq11.fsf@jpl.org>
2004-11-11 7:40 ` Katsumi Yamaoka
2004-11-11 11:18 ` Katsumi Yamaoka
2004-11-11 17:45 ` Luc Teirlinck
2004-11-11 21:55 ` Stefan
2004-11-11 22:41 ` Luc Teirlinck
2004-11-11 22:54 ` Luc Teirlinck
2004-11-12 0:22 ` Katsumi Yamaoka
2004-11-12 3:57 ` Stefan Monnier
2004-11-12 4:30 ` Katsumi Yamaoka
2004-11-13 23:03 ` Stefan
2004-11-14 0:14 ` Katsumi Yamaoka
2004-11-14 5:21 ` Stefan
2004-11-14 6:10 ` Katsumi Yamaoka
2004-11-14 6:36 ` Stefan
2004-11-14 13:44 ` Katsumi Yamaoka [this message]
2004-11-14 17:29 ` Luc Teirlinck
2004-11-14 19:17 ` Stefan Monnier
2004-11-15 14:00 ` Richard Stallman
2004-11-15 15:36 ` Stefan Monnier
2004-11-15 23:22 ` Miles Bader
2004-11-15 23:28 ` Stefan Monnier
2004-11-15 23:38 ` Miles Bader
2004-11-15 23:44 ` Stefan Monnier
2004-11-15 23:57 ` Luc Teirlinck
2004-11-16 1:29 ` Nick Roberts
2004-11-16 1:49 ` Luc Teirlinck
2004-11-16 2:19 ` Luc Teirlinck
2004-11-16 16:49 ` Richard Stallman
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=yotl4qjs5yv9.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=teirllm@dms.auburn.edu \
/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 NNTP newsgroup(s).