unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Daniel Colascione <dancol@dancol.org>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: Should we just start dumping cl-lib?
Date: Fri, 02 Oct 2015 14:21:18 +0200	[thread overview]
Message-ID: <874mi9a2bl.fsf@igel.home> (raw)
In-Reply-To: <CAAdUY-+pA_WBO_wVVN9PAi4q4RfNGqbbKvM+w64RFx2YMh1Bkg@mail.gmail.com> (Artur Malabarba's message of "Fri, 2 Oct 2015 09:23:48 +0100")

Artur Malabarba <bruce.connor.am@gmail.com> writes:

> This might still be an instance of (b), given how many packages require
> cl-lib.

They should require it only during compiling.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



  reply	other threads:[~2015-10-02 12:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02  4:52 Should we just start dumping cl-lib? Daniel Colascione
2015-10-02  5:12 ` John Wiegley
2015-10-02  5:28   ` Daniel Colascione
2015-10-02  7:19     ` Eli Zaretskii
2015-10-02  8:07       ` Eli Zaretskii
2015-10-02  8:23       ` Artur Malabarba
2015-10-02 12:21         ` Andreas Schwab [this message]
2015-10-02 12:38           ` Artur Malabarba
2015-10-02 14:27             ` Rasmus
2015-10-02  7:21     ` Oleh Krehel
2015-10-02 11:46 ` Mark Oteiza
2015-10-02 13:37   ` Tassilo Horn
2015-10-02 15:22     ` Artur Malabarba
2015-10-02 13:45   ` Eli Zaretskii
2015-10-02 14:14     ` Mark Oteiza
2015-10-02 14:18       ` Eli Zaretskii
2015-10-02 14:22         ` Mark Oteiza
2015-10-02 14:38           ` Eli Zaretskii
2015-10-02 16:07     ` John Wiegley
2015-10-03  0:19       ` Daniel Colascione
2015-10-03  7:22         ` Eli Zaretskii
2015-10-04  1:24           ` Daniel Colascione
2015-10-04  6:48             ` Eli Zaretskii
2015-10-02 15:13   ` Nicolas Petton

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=874mi9a2bl.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=bruce.connor.am@gmail.com \
    --cc=dancol@dancol.org \
    --cc=eliz@gnu.org \
    --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).