From: Phil Sainty <psainty@orcon.net.nz>
To: emacs-devel@gnu.org
Subject: Re: gnu.org-hosted external repositories for GNU ELPA packages?
Date: Sun, 5 Jun 2016 02:13:27 +1200 [thread overview]
Message-ID: <5752E207.7040905@orcon.net.nz> (raw)
In-Reply-To: <jwv60tqj60u.fsf-monnier+gmane.emacs.devel@gnu.org>
Hi Stefan,
I guess my question is really just: Can I register each of my Emacs
packages as a git repository at savannah.gnu.org?
I do understand that all of GNU ELPA is built from the main repository,
but I wouldn't expect to get access to push arbitrary changes to that
repository, so my understanding is that in order to have changes
pushed I would need to send them to this list -- which is absolutely
fine for stable releases, but pointlessly noisy for work-in-progress
commits.
So I'm looking to have external repositories where pre-release versions
can be developed, with stable versions being merged to the GNU ELPA
repository when ready.
Savannah sounds like the right option, but I've never used it before,
so I was hoping for confirmation that it's a valid option.
> GNU ELPA's packages are prepared from the elpa.git repository (among
> other reasons, so as to make sure every code distributed was installed
> by people who have commit access and signed paperwork).
I have signed paperwork for Emacs contributions. If contributing to
GNU ELPA means I get commit access to the main repository, I can deal
with that. It would just be surprising to me (and not my preferred
option), but if that's actually how it works, then that's ok.
-Phil
On 04/06/16 09:54, Stefan Monnier wrote:
>> My preference would be to maintain them as external git repositories
>> so that I can push work-in-progress without bothering the emacs-devel
>> list, and only notify emacs-devel once I was happy for a new version
>> to be looked at.
>
> GNU ELPA's packages are prepared from the elpa.git repository (among
> other reasons, so as to make sure every code distributed was installed
> by people who have commit access and signed paperwork).
>
> So elpa.git needs to have a copy of the repository. The canonical
> repository can be elsewhere (and you just need to "push" to elpa.git
> in order to release a new version).
>
> Note that other people may still install changes in the elpa.git copy
> (you should then get an automatic email message with that change).
>
>
> Stefan
>
>
next prev parent reply other threads:[~2016-06-04 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 12:45 gnu.org-hosted external repositories for GNU ELPA packages? Phil Sainty
2016-06-03 21:54 ` Stefan Monnier
2016-06-04 14:13 ` Phil Sainty [this message]
2016-06-04 16:57 ` Stefan Monnier
2016-06-04 22:36 ` Phil Sainty
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=5752E207.7040905@orcon.net.nz \
--to=psainty@orcon.net.nz \
--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.