unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: chad <yandros@gmail.com>
To: EMACS development team <emacs-devel@gnu.org>,
	Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>
Cc: Payas Relekar <relekarpayas@gmail.com>,
	John Wiegley <jwiegley@gmail.com>,
	 Philip Kaludercic <philipk@posteo.net>
Subject: Re: Progress on merging use-package?
Date: Wed, 28 Sep 2022 18:57:26 -0400	[thread overview]
Message-ID: <CAO2hHWbko8x_U+8YhcwTEW=4QeDz8w5+92mmmvedQcehVrWiFw@mail.gmail.com> (raw)
In-Reply-To: <87o7v37sqh.fsf@posteo.net>

[-- Attachment #1: Type: text/plain, Size: 829 bytes --]

Eli & Lars, as a point of clarification: what would you want to see in
terms of integration into core for use-package to make the late-November
cut for emacs 29.1?

My understanding is that the copyright concerns are cleared, but John
(Weigley, for anyone looking at this later) believes that some
documentation work needs to be done. He doesn't have time to do it himself,
but there do seem to be some potential volunteers (tentatively including
myself).

I expect that _eventually_ relatively deep documentation changes would be
wanted if it were included in core (both to use-package and to
emacs's existing documentation), but that it might be ok to include the
package (with correct documentation) in 29.1 without necessarily pushing it
throughout all of emacs' own documentation. Does that sound reasonable?

Thanks,
~Chad

[-- Attachment #2: Type: text/html, Size: 954 bytes --]

  reply	other threads:[~2022-09-28 22:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24 12:56 Progress on merging use-package? Payas Relekar
2022-09-24 14:08 ` Philip Kaludercic
2022-09-24 14:22   ` Payas Relekar
2022-09-24 14:35     ` Philip Kaludercic
2022-09-24 14:36       ` Payas Relekar
2022-09-24 15:51         ` Philip Kaludercic
2022-09-24 20:24         ` John Wiegley
2022-09-25  2:34           ` Payas Relekar
2022-09-25  2:45             ` Payas Relekar
2022-09-25  8:09               ` Philip Kaludercic
2022-09-25  8:39             ` Philip Kaludercic
2022-09-28 22:57               ` chad [this message]
2022-09-29  8:20                 ` Eli Zaretskii
2022-09-29  8:36                   ` Philip Kaludercic
2022-10-07 22:47                     ` What does use-package do? Richard Stallman
2022-10-08  4:50                       ` John Wiegley
2022-09-24 15:42   ` Progress on merging use-package? Stefan Monnier

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='CAO2hHWbko8x_U+8YhcwTEW=4QeDz8w5+92mmmvedQcehVrWiFw@mail.gmail.com' \
    --to=yandros@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jwiegley@gmail.com \
    --cc=larsi@gnus.org \
    --cc=philipk@posteo.net \
    --cc=relekarpayas@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 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).