From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Fabian Ezequiel Gallina <galli.87@gmail.com>
Cc: johnw@gnu.org, Jorgen Schaefer <forcer@forcix.cx>, emacs-devel@gnu.org
Subject: Re: Replacing the `elpa' branch
Date: Sun, 10 Mar 2013 00:18:52 -0500 [thread overview]
Message-ID: <jwv4ngj6exc.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CABq4mQvGQx9rcn=7bJg7z3BCxRsQFauQPRi0JkkZsC3g9OMvBQ@mail.gmail.com> (Fabian Ezequiel Gallina's message of "Sat, 9 Mar 2013 02:02:06 -0300")
>> Let me know here or over e-mail what needs to be done. I plan to do
>> some work with the ELPA anyhow after the 24.3 release (to address the
>> things that came up during the ELPA security discussion).
> What's the status of the ELPA branch replacement?
Haven't had time to devote to it. AFAIK, there's a Git version of the
branch (prepared by Joergen), with the following needs:
1- update it to ELPA's tip.
2- install it somehow into git.sv.gnu.org.
3- update the scripts on elpa.gnu.org.
I think the first step now is to figure out how to do step 2.
Once this is settled, we can do step 1 and then 2. Step 3 can come
later without too much trouble.
Stefan
next prev parent reply other threads:[~2013-03-10 5:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 20:33 Replacing the `elpa' branch Stefan Monnier
2013-02-16 14:06 ` Richard Stallman
2013-02-16 14:31 ` Stefan Monnier
2013-02-18 6:33 ` Leo Liu
2013-02-25 16:32 ` Ted Zlatanov
2013-03-09 5:02 ` Fabian Ezequiel Gallina
2013-03-10 5:18 ` Stefan Monnier [this message]
2013-03-10 8:06 ` Andreas Schwab
2013-03-10 10:19 ` Jorgen Schaefer
2013-03-10 11:57 ` Andreas Schwab
2013-03-10 12:06 ` Jorgen Schaefer
2013-03-10 16:35 ` Andreas Schwab
2013-03-10 12:44 ` Achim Gratz
2013-03-10 16:51 ` Jorgen Schaefer
2013-03-10 17:37 ` Dmitry Gutov
2013-03-10 17:41 ` Jorgen Schaefer
2013-03-10 18:52 ` Andreas Schwab
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=jwv4ngj6exc.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=forcer@forcix.cx \
--cc=galli.87@gmail.com \
--cc=johnw@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.