From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Nic Ferrier Newsgroups: gmane.emacs.devel Subject: Re: GNU ELPA; mw 0.1: modular MediaWiki interface for Emacs Date: Wed, 15 Oct 2014 19:51:17 +0100 Message-ID: <87iojli2u2.fsf@ferrier.me.uk> References: <87oatpkof7.fsf@passepartout.tim-landscheidt.de> <87r3ye3mf7.fsf@violet.siamics.net> <87zjd1zj0q.fsf@violet.siamics.net> <87k342zabt.fsf@violet.siamics.net> <87zjcxy6eh.fsf_-_@violet.siamics.net> <87y4shsbf4.fsf@ferrier.me.uk> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1413399124 23356 80.91.229.3 (15 Oct 2014 18:52:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 15 Oct 2014 18:52:04 +0000 (UTC) Cc: Ivan Shmakov , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 15 20:51:57 2014 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 1XeTfv-0005V5-U2 for ged-emacs-devel@m.gmane.org; Wed, 15 Oct 2014 20:51:56 +0200 Original-Received: from localhost ([::1]:46291 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XeTfv-0000Ck-Ka for ged-emacs-devel@m.gmane.org; Wed, 15 Oct 2014 14:51:55 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42971) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XeTfb-0000Bn-Ud for emacs-devel@gnu.org; Wed, 15 Oct 2014 14:51:41 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XeTfQ-0004Hz-Qh for emacs-devel@gnu.org; Wed, 15 Oct 2014 14:51:35 -0400 Original-Received: from static.17.66.46.78.clients.your-server.de ([78.46.66.17]:41724 helo=po1.ferrier.me.uk) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XeTfQ-0004HY-L8 for emacs-devel@gnu.org; Wed, 15 Oct 2014 14:51:24 -0400 Original-Received: from nicferrier-dell-xps (140.35.155.90.in-addr.arpa [90.155.35.140]) by po1.ferrier.me.uk (Postfix) with ESMTPA id 25BC2AC02D9; Wed, 15 Oct 2014 21:08:04 +0200 (CEST) Original-Received: from nicferrier-XPS13-9333 (localhost [127.0.0.1]) by nicferrier-dell-xps (Postfix) with ESMTPS id 38EEB6023A; Wed, 15 Oct 2014 19:51:18 +0100 (BST) In-Reply-To: (Stefan Monnier's message of "Wed, 15 Oct 2014 13:51:01 -0400") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 78.46.66.17 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:175429 Archived-At: Stefan Monnier writes: > > Now I understand you suggest we use Marmalade's scripts to manage the > GNU ELPA archive, but I still don't know what that means concretely. > > The fact that we have a local storage of the source and VCS history > (with write access so that any Emacs maintainer can install fixes) is an > important design choice. Would that easily fit into Marmalade's > code base? How does Marmalade track commits to send them back to the > respective package's maintainer? It doesn't. You just upload the resulting package. Hence avoiding the problem of managing the commits. The author does that. Nic