From: Bozhidar Batsov <bozhidar@batsov.com>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: subr-x on Elpa
Date: Wed, 20 May 2015 18:35:02 +0300 [thread overview]
Message-ID: <CAM9Zgm2acJx0SJzd3+YFfm_tzpc2Ue2kuSq7Z9ecNesyeaJkXw@mail.gmail.com> (raw)
In-Reply-To: <CAAdUY-Jf5k5hr+i_eh6e=0yNezULRQMLqbbZ0a9d5djs2dRySA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
Not sure how wise it is to package something that acts as a staging ground
for things to be promoted in say subr.el, as a package. This was the
original idea behind subr-x.el - I had suggested some things to be added to
subr.el, but they were deemed somewhat experimental, as some people weren't
convinced of their usefulness. So, provided things get moved from subr-x to
subr, which I hope to see some day, this proposed package will get out of
sync with whatever is in Emacs itself.
On 20 May 2015 at 17:33, Artur Malabarba <bruce.connor.am@gmail.com> wrote:
> > > If I do that, would it be viable to offer subr-x on GNU Elpa as well?
> >
> > Like we do for seq.el?
>
> Yes, precisely.
>
> > I don't like this duplication very much, but as
> > long as they are 100% identical, I think it's OK.
>
> I'm never a fan of redundancy, but in this case I think it's worth the
> evil.
> But it would certainly be nice to have a way to link the source of an Elpa
> package to its built-in counterpart.
>
[-- Attachment #2: Type: text/html, Size: 1453 bytes --]
next prev parent reply other threads:[~2015-05-20 15:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 12:32 subr-x on Elpa Artur Malabarba
2015-05-20 14:07 ` Stefan Monnier
2015-05-20 14:33 ` Artur Malabarba
2015-05-20 15:35 ` Bozhidar Batsov [this message]
2015-05-20 19:04 ` Artur Malabarba
2015-05-20 18:51 ` Stefan Monnier
2015-05-20 19:02 ` joakim
2015-05-20 19:13 ` Eli Zaretskii
2015-05-20 20:46 ` Stefan Monnier
2015-05-21 10:28 ` Dmitry Gutov
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=CAM9Zgm2acJx0SJzd3+YFfm_tzpc2Ue2kuSq7Z9ecNesyeaJkXw@mail.gmail.com \
--to=bozhidar@batsov.com \
--cc=bruce.connor.am@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).