From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Add autoload cookies in seq.el
Date: Fri, 22 Jul 2016 06:50:58 -0400 [thread overview]
Message-ID: <87oa5q54kt.fsf@lifelogs.com> (raw)
In-Reply-To: m3h9bixcvx.fsf@gnus.org
On Fri, 22 Jul 2016 11:04:02 +0200 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> Eli Zaretskii <eliz@gnu.org> writes:
>> So my memory was correct in this case. I'd like this library to have
>> more (potential) users before we preload it (and its prerequisites).
LI> OK; so somebody else (who has to be unaware that we can't use seq
LI> functions in the central Lisp files) has to add something dependent on
LI> seq a couple of times, and then it'll have to be rewritten by a
LI> different maintainer a couple of times, and then it'll be OK.
That seems reasonable. We just need some seq puppets. (collective groan)
Ted
next prev parent reply other threads:[~2016-07-22 10:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 6:06 Add autoload cookies in seq.el Tino Calancha
2016-05-20 8:26 ` Nicolas Petton
2016-05-20 8:54 ` Tino Calancha
2016-05-20 9:42 ` Eli Zaretskii
2016-05-21 0:07 ` Tino Calancha
2016-05-21 6:50 ` Eli Zaretskii
2016-07-20 13:24 ` Lars Ingebrigtsen
2016-07-20 15:13 ` Eli Zaretskii
2016-07-21 10:51 ` Lars Ingebrigtsen
2016-07-21 13:27 ` Ted Zlatanov
2016-07-21 14:38 ` Eli Zaretskii
2016-07-21 14:33 ` Eli Zaretskii
2016-07-21 15:01 ` Lars Ingebrigtsen
2016-07-21 16:09 ` Eli Zaretskii
2016-07-22 9:04 ` Lars Ingebrigtsen
2016-07-22 10:50 ` Ted Zlatanov [this message]
2016-07-21 14:36 ` Michael Heerdegen
2016-07-21 15:45 ` Stefan Monnier
2016-07-22 14:26 ` Stefan Monnier
2016-07-22 15:07 ` Nicolas Petton
2016-07-22 15:18 ` Stefan Monnier
2016-07-22 15:28 ` Eli Zaretskii
2016-07-22 17:48 ` Nicolas Petton
2016-05-22 12:17 ` Tino Calancha
2016-05-22 19:54 ` Nicolas Petton
2016-05-23 1:49 ` Tino Calancha
2016-05-23 8:33 ` Nicolas Petton
2016-05-23 15:13 ` 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=87oa5q54kt.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.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).