From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: How does ELPA work?
Date: Wed, 02 Mar 2011 08:41:07 -0600 [thread overview]
Message-ID: <87d3m9pou4.fsf@lifelogs.com> (raw)
In-Reply-To: m3aahdoonb.fsf@verona.se
On Wed, 02 Mar 2011 10:30:32 +0100 joakim@verona.se wrote:
j> I would like, as an example, for Jan Morringens very useful d-bus proxy
j> library to be available through ELPA if not in the core.
j> How can I help make that happen? I haven't been able to figure out how
j> the GNU ELPA repo works. There is supposed to be a bzr branch somewhere
j> right? Do I have access to that as an Emacs comitter? Can Jan be given
j> that access?
Chong Yidong has been handling the copyright assignments.
The GNU ELPA is in the elpa branch, accessible as
bzr://bzr.savannah.gnu.org/emacs/elpa/ and AFAIK without any special
permissions compared to the Emacs trunk. But deploying from that branch
to elpa.gnu.org is a semi-manual process. See admin/package-update.sh
in the elpa branch for details on what actually happens, it's pretty
simple..
Assuming the assignment is in order, either I or one of the maintainers
can do the deployment.
Ted
next prev parent reply other threads:[~2011-03-02 14:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 9:30 How does ELPA work? joakim
2011-03-02 14:41 ` Ted Zlatanov [this message]
2011-03-05 21:09 ` Michael Albinus
2011-03-05 21:24 ` Chong Yidong
2011-03-06 22:05 ` Chong Yidong
2011-03-07 14:12 ` Michael Albinus
2011-03-08 0:25 ` Chong Yidong
2011-03-08 3:03 ` Stefan Monnier
2011-03-08 17:11 ` Chong Yidong
2011-03-08 13:03 ` Michael Albinus
2011-03-08 17:09 ` Chong Yidong
2011-03-08 17:56 ` Michael Albinus
2011-03-08 18:34 ` Chong Yidong
2011-03-08 18:48 ` Ted Zlatanov
2011-03-08 19:52 ` Michael Albinus
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=87d3m9pou4.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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 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.