unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Payas Relekar <relekarpayas@gmail.com>
To: John Wiegley <jwiegley@gmail.com>
Cc: Philip Kaludercic <philipk@posteo.net>, emacs-devel@gnu.org
Subject: Re: Progress on merging use-package?
Date: Sun, 25 Sep 2022 08:15:04 +0530	[thread overview]
Message-ID: <8735cgcgsz.fsf@gmail.com> (raw)
In-Reply-To: <877d1scgyv.fsf@gmail.com>


Correction, Stefan has a patch for ELPA :)

Payas Relekar <relekarpayas@gmail.com> writes:

> Thank you John!
>
> John Wiegley <jwiegley@gmail.com> writes:
>
>> I'd be happy to serve as supporting developer if someone else is willing to
>> spearhead this effort on the docs and integration side. If you run into any
>> issues, e-mail me directly and I'll be happy to help, but if it waits on me to
>> get the documentation and proper build infrastructure together, I'm afraid it
>> won't happen.
>
> Alright, I'll try my hand. It will be slow going, for I am but a noob,
> and most likely not happen before 29 branch is cut, but thats the plan.
>
> Combining Philip's steps here, the plan is:
>
> 1. Get use-package in ELPA
>    Philip already has a patch ready to be reviewed
> 2. Complete all documentation
>    Not sure what it means to 'complete', but I'll go through it, try
>    to make it in more tutorial-esque.
> 3. Prepare documentation in texinfo
>    Will cross that bridge when 2 is done.
> 4. Add all relevant files to emacs.git
>    TBD when 3 is done.
> 5. Ensure everything loads properly
>    TBD when 4 is done. This part will probably need testing from wider
>    community, but its out enough in the future that I don't want to
>    think about it right now.
>
> Philip, would you have any pointer to get started on #2?
>
> Thanks,
> Payas


--



  reply	other threads:[~2022-09-25  2:45 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 [this message]
2022-09-25  8:09               ` Philip Kaludercic
2022-09-25  8:39             ` Philip Kaludercic
2022-09-28 22:57               ` chad
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=8735cgcgsz.fsf@gmail.com \
    --to=relekarpayas@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=jwiegley@gmail.com \
    --cc=philipk@posteo.net \
    /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).