From: Benjamin Orthen <benjamin@orthen.net>
To: 63916@debbugs.gnu.org
Subject: bug#63916: 30.0.50; use-package: changes do not propagate to elpa-devel
Date: Mon, 05 Jun 2023 23:21:54 +0200 [thread overview]
Message-ID: <4b1ff1660351348f3d5f1bc848965d59@orthen.net> (raw)
Recent changes in use-package (i.e., commit
2ce279680bf9c1964e98e2aa48a03d6675c386fe) have not propagated to
emacs-devel (https://elpa.gnu.org/devel/use-package.html) even though
use-package is designated as a :core package in elpa.
My understanding is that changes in emacs for :core packages are
automatically propagated to elpa(-devel). I was however not able to find
documentation on how this propagation/sync works. I noticed that
use-package.el does not have the disclaimer ";; This is a GNU ELPA :core
package. Avoid adding functionality [...]" in its header. I suppose this
is unrelated to the elpa-devel sync, but could be fixed as well.
Best regards,
Benjamin
next reply other threads:[~2023-06-05 21:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 21:21 Benjamin Orthen [this message]
2023-06-10 9:03 ` bug#63916: 30.0.50; use-package: changes do not propagate to elpa-devel Philip Kaludercic
2023-06-10 16:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-11 10:34 ` Philip Kaludercic
2023-06-11 15:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-11 16:37 ` Philip Kaludercic
2023-06-11 16:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-11 17:32 ` Benjamin Orthen
2023-09-08 10:55 ` Benjamin Orthen
2023-09-08 17:14 ` Philip Kaludercic
2023-09-08 19:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11 9:58 ` Benjamin Orthen
2023-09-27 10:53 ` Benjamin Orthen
2023-09-28 19:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=4b1ff1660351348f3d5f1bc848965d59@orthen.net \
--to=benjamin@orthen.net \
--cc=63916@debbugs.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 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.