From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: emacs->gnus merge questions
Date: Sat, 08 Dec 2007 22:29:40 +0100 [thread overview]
Message-ID: <v98x44j2nv.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87y7c4j34q.fsf@catnip.gol.com>
On Sat, Dec 08 2007, Miles Bader wrote:
> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>> (eval-and-compile
>> (unless (fboundp 'declare-function) (defmacro declare-function (&rest r))))
>
> Defining standard functions is a very bad idea in general. Better to
> use the standard Gnus approach of a special `gnus-declare-function' or
> whatever (yeah it's ugly, but...).
That was my first reaction too, but Richard and other Emacs developers
say it is okay in this case:
<http://thread.gmane.org/gmane.emacs.devel/84621>
>> merge_to_emacs_trunk
>> merge_from_emacs_trunk
>> merge_to_emacs_22
>> merge_from_emacs_22
>
> Ok.
Thanks. (Feel free to suggest better names.)
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2007-12-08 21:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-08 3:24 Miles Bader
2007-12-08 19:38 ` Reiner Steib
2007-12-08 21:19 ` Miles Bader
2007-12-08 21:29 ` Reiner Steib [this message]
2007-12-08 23:32 ` Miles Bader
2007-12-08 23:45 ` Miles Bader
2008-02-16 13:24 ` encrypt.el (was: emacs->gnus merge questions) Reiner Steib
2008-02-16 13:26 ` assistant.el " Reiner Steib
2007-12-11 16:22 ` emacs->gnus merge questions Ted Zlatanov
2007-12-17 23:02 ` Ted Zlatanov
2007-12-17 23:03 ` Ted Zlatanov
2007-12-18 20:25 ` Ted Zlatanov
2007-12-18 22:52 ` encrypt.el glue to PGG library added (was: emacs->gnus merge questions) Ted Zlatanov
2008-02-16 13:12 ` encrypt.el " Reiner Steib
2008-02-28 14:55 ` encrypt.el Ted Zlatanov
2008-02-28 20:28 ` encrypt.el Reiner Steib
2008-03-10 15:06 ` encrypt.el Ted Zlatanov
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=v98x44j2nv.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.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).