unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuchen Pei <id@ypei.org>
To: Emacs Devel mailing list <emacs-devel@gnu.org>
Subject: How Do I submit a package to ELPA? (was Re: [ELPA] New package: hcel)
Date: Mon, 19 Sep 2022 10:15:57 +1000	[thread overview]
Message-ID: <87h714w75u.fsf_-_@ypei.org> (raw)
In-Reply-To: <87wna2x27g.fsf@ypei.org> (Yuchen Pei's message of "Sat, 17 Sep 2022 10:40:51 +1000")

On Sat 2022-09-17 10:40:51 +1000, Yuchen Pei wrote:

> Given there's no comments and no approval process[1], my next step will
> be to prepare the package further for elpa publication, including
> separating the emacs package out from the repo due to copyright
> assignment, and ask here for someone with commit access to push my
> package to an hcel branch on elpa.git.  I will try to do that over the
> weekend.
>
> [1] https://git.savannah.gnu.org/cgit/emacs/elpa.git/plain/README

I just noticed that the instructions on adding a package to ELPA is
below the following text:

* Text below this marker is OUTDATED and still needs to be reviewed/rewritten!!

So I'm not sure what to do now.  What is the diff between the current
process and the instructions in the README?

Best,
Yuchen

-- 
PGP Key: 47F9 D050 1E11 8879 9040  4941 2126 7E93 EF86 DFD0
          <https://ypei.org/assets/ypei-pubkey.txt>



  reply	other threads:[~2022-09-19  0:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-10 15:01 [ELPA] New package: hcel Yuchen Pei
2022-09-17  0:40 ` Yuchen Pei
2022-09-19  0:15   ` Yuchen Pei [this message]
2022-09-20 21:26 ` Stefan Monnier
2022-09-21  6:18   ` Yuchen Pei
2022-09-21 12:03     ` Stefan Monnier
2022-09-20 21:42 ` Stefan Monnier
2022-09-21  5:58   ` Yuchen Pei
2022-09-21  6:21     ` Stefan Kangas
2022-09-21  7:19     ` Michael Heerdegen
2022-09-21  7:44       ` Emanuel Berg

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=87h714w75u.fsf_-_@ypei.org \
    --to=id@ypei.org \
    --cc=emacs-devel@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 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).