From: Chong Yidong <cyd@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ofv@wanadoo.es, Paul Eggert <eggert@cs.ucla.edu>,
schwab@linux-m68k.org, emacs-devel@gnu.org
Subject: Re: External inline functions
Date: Tue, 08 Nov 2011 17:59:09 +0800 [thread overview]
Message-ID: <87k47b7x5e.fsf@gnu.org> (raw)
In-Reply-To: <83y5vsio89.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 07 Nov 2011 05:51:50 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> how about if we simply stop using extern inline functions?
>
> That'd be my suggestion as well, if no one objects.
Fine by me.
next prev parent reply other threads:[~2011-11-08 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 18:36 External inline functions Eli Zaretskii
2011-11-06 19:00 ` Andreas Schwab
2011-11-06 20:39 ` Óscar Fuentes
2011-11-06 21:20 ` Paul Eggert
2011-11-07 3:51 ` Eli Zaretskii
2011-11-08 9:59 ` Chong Yidong [this message]
2011-11-08 20:07 ` Paul Eggert
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=87k47b7x5e.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
--cc=schwab@linux-m68k.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).