From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: compile warn
Date: Fri, 26 Nov 2004 17:15:05 +0900 [thread overview]
Message-ID: <b9yllcprppy.fsf@jpl.org> (raw)
In-Reply-To: <b9ybrdn1zcm.fsf@jpl.org>
>>>>> In <b9ybrdn1zcm.fsf@jpl.org> Katsumi Yamaoka wrote:
> Since bytecomp.el has been changed in the Emacs trunk, Gnus got
> to issue many warnings while compiling and I am always startled
> with them even if they don't cause any problems and are
> negligible. In order to silence those warnings, I made a patch
> to nnrss.el and spam.el. Am I able to commit it?
> A patch for the Gnus trunk: http://www.jpl.org/trunk-patch.txt
> A patch for the v5-10 branch: http://www.jpl.org/v5-10-patch.txt
I've modified and installed them. It is useful at least for me
that bogus warnings aren't issued while building Gnus. It makes
it easy to find out serious problems. Although they aren't
helpful while building Emacs, the reason I also modified the
v5-10 branch is that it will be released as Gnus v5.10.7.
Regards,
next prev parent reply other threads:[~2004-11-26 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 7:27 Katsumi Yamaoka
2004-11-26 8:15 ` Katsumi Yamaoka [this message]
2004-11-26 8:46 ` Katsumi Yamaoka
2004-11-26 9:13 ` Katsumi Yamaoka
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=b9yllcprppy.fsf@jpl.org \
--to=yamaoka@jpl.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 NNTP newsgroup(s).