From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Phil Sainty Newsgroups: gmane.emacs.devel Subject: Re: gnu.org-hosted external repositories for GNU ELPA packages? Date: Sun, 5 Jun 2016 02:13:27 +1200 Message-ID: <5752E207.7040905@orcon.net.nz> References: <57517BEF.10408@orcon.net.nz> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1465049639 7796 80.91.229.3 (4 Jun 2016 14:13:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 4 Jun 2016 14:13:59 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 04 16:13:47 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1b9CKg-0001OJ-TN for ged-emacs-devel@m.gmane.org; Sat, 04 Jun 2016 16:13:47 +0200 Original-Received: from localhost ([::1]:32821 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b9CKg-00058p-1F for ged-emacs-devel@m.gmane.org; Sat, 04 Jun 2016 10:13:46 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42479) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b9CKa-00058Z-9g for emacs-devel@gnu.org; Sat, 04 Jun 2016 10:13:41 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b9CKV-0001Km-8L for emacs-devel@gnu.org; Sat, 04 Jun 2016 10:13:39 -0400 Original-Received: from [219.88.242.62] (port=60125 helo=mail.orcon.net.nz) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b9CKU-0001KI-Nz for emacs-devel@gnu.org; Sat, 04 Jun 2016 10:13:35 -0400 Original-Received: from [192.168.20.100] (host-203-94-60-222.xdsl.kinect.net.nz [203.94.60.222] (may be forged)) (authenticated bits=0) by mail.orcon.net.nz (8.14.3/8.14.3/Debian-9.4) with ESMTP id u54EDRS6024067 for ; Sun, 5 Jun 2016 02:13:28 +1200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 In-Reply-To: X-Bayes-Prob: 0.0001 (Score 0: No Bayes scoring rules defined, tokens from: outbound) X-CanIt-Geo: ip=203.94.60.222; country=NZ; region=Auckland; city=Auckland; latitude=-36.8667; longitude=174.7667; http://maps.google.com/maps?q=-36.8667,174.7667&z=6 X-CanItPRO-Stream: base:outbound X-Canit-Stats-ID: 02R2CdsWi - 06391e116494 - 20160605 (trained as not-spam) X-Scanned-By: CanIt (www . roaringpenguin . com) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 219.88.242.62 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:204194 Archived-At: 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 > >