From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>, John Wiegley <johnw@gnu.org>
Cc: jonas@bernoul.li, monnier@iro.umontreal.ca, 62751@debbugs.gnu.org
Subject: bug#62751: 29.0.90; New libraries that still need to be assigned to packages
Date: Thu, 21 Sep 2023 10:15:07 +0300 [thread overview]
Message-ID: <83pm2c9ev8.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmn3tohLpwUwkTynKTXTQHvpiV_pktRTsLXzHxRDhFczZA@mail.gmail.com> (message from Stefan Kangas on Wed, 20 Sep 2023 17:15:04 -0700)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Wed, 20 Sep 2023 17:15:04 -0700
> Cc: jonas@bernoul.li, 62751@debbugs.gnu.org, monnier@iro.umontreal.ca
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> > You mean, move bind-key.el out of lisp/use-package, right?
> >>
> >> Yes.
> >
> > Fine by me, and I think this is preferable, and even clearly TRT for a
> > package that is not limited to its parent package.
>
> Do you see any reason why that change would be dangerous, or could we do
> it on the release branch?
I honestly don't know. Maybe we should ask the users of use-package?
John, do you see any potential problems with that?
One issue to consider is what will happen to use-package and bind-key
on ELPA -- will you make bind-key a separate package there??
next prev parent reply other threads:[~2023-09-21 7:15 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 13:04 bug#62751: 29.0.90; New libraries that still need to be assigned to packages Jonas Bernoulli
2023-04-10 13:30 ` Eli Zaretskii
2023-04-11 16:03 ` Michael Albinus
2023-04-11 17:16 ` Jonas Bernoulli
2023-09-05 23:49 ` Stefan Kangas
2023-09-16 9:21 ` Stefan Kangas
2023-09-16 14:23 ` Stefan Kangas
2023-09-17 22:06 ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-18 7:34 ` Stefan Kangas
2023-09-18 11:02 ` Eli Zaretskii
2023-09-18 11:10 ` Stefan Kangas
2023-09-18 11:49 ` Eli Zaretskii
2023-09-21 0:15 ` Stefan Kangas
2023-09-21 2:29 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-21 7:26 ` Stefan Kangas
2023-09-21 14:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-22 12:36 ` Stefan Kangas
2023-09-21 7:15 ` Eli Zaretskii [this message]
2023-09-21 7:29 ` Stefan Kangas
2023-09-23 14:42 ` Stefan Kangas
2023-09-24 18:07 ` John Wiegley
2023-09-24 20:22 ` Stefan Kangas
2023-09-24 21:05 ` John Wiegley
2023-09-26 22:37 ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-18 11:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-21 0:06 ` Stefan Kangas
2023-09-18 15:19 ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-20 15:59 ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-24 12:29 ` Stefan Kangas
2023-10-01 13:11 ` Stefan Kangas
2023-10-01 13:56 ` Eli Zaretskii
2023-10-01 15:46 ` Stefan Kangas
2023-10-01 16:52 ` Eli Zaretskii
2023-10-01 17:46 ` Stefan Kangas
2023-09-18 15:33 ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-21 0:04 ` Stefan Kangas
2023-09-21 21:12 ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-22 15:30 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-23 11:35 ` Stefan Kangas
2023-10-13 23:33 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14 6:45 ` Eli Zaretskii
2023-10-14 14:39 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14 16:21 ` Stefan Kangas
2023-09-19 23:12 ` Richard Stallman
2023-09-20 23:45 ` Stefan Kangas
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=83pm2c9ev8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62751@debbugs.gnu.org \
--cc=johnw@gnu.org \
--cc=jonas@bernoul.li \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.