From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: policy discussion on bundling ELPA packages in the emacs tarball Date: Wed, 27 Jan 2021 18:22:11 +0200 Message-ID: <83r1m6z6x8.fsf@gnu.org> References: <86eeifawx8.fsf@stephe-leake.org> <87czxygdl9.fsf@russet.org.uk> <86tur88izp.fsf@stephe-leake.org> <86h7n880lo.fsf@stephe-leake.org> <83y2gk3rin.fsf@gnu.org> <86o8he6y4k.fsf@stephe-leake.org> <8335yq4350.fsf@gnu.org> <86k0s26qqt.fsf@stephe-leake.org> <83sg6q2is5.fsf@gnu.org> <7d85c33d-5f9c-e4b4-c37a-121bee411465@yandex.ru> <86o8hc65js.fsf@stephe-leake.org> <83mtwv21qj.fsf@gnu.org> <8635ym5tu2.fsf@stephe-leake.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33463"; mail-complaints-to="usenet@ciao.gmane.io" Cc: phillip.lord@russet.org.uk, emacs-devel@gnu.org, dgutov@yandex.ru To: Stephen Leake Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jan 27 17:22:47 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l4nah-0008co-2s for ged-emacs-devel@m.gmane-mx.org; Wed, 27 Jan 2021 17:22:47 +0100 Original-Received: from localhost ([::1]:41394 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l4nag-0007aC-2I for ged-emacs-devel@m.gmane-mx.org; Wed, 27 Jan 2021 11:22:46 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48382) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l4nZw-0006VB-1t for emacs-devel@gnu.org; Wed, 27 Jan 2021 11:22:00 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:49920) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l4nZv-0007UL-0e; Wed, 27 Jan 2021 11:21:59 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1400 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1l4nZt-00037D-Fl; Wed, 27 Jan 2021 11:21:58 -0500 In-Reply-To: <8635ym5tu2.fsf@stephe-leake.org> (message from Stephen Leake on Wed, 27 Jan 2021 06:37:41 -0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:263512 Archived-At: > From: Stephen Leake > Cc: dgutov@yandex.ru, phillip.lord@russet.org.uk, emacs-devel@gnu.org > Date: Wed, 27 Jan 2021 06:37:41 -0800 > > > By "branch" here do you mean an elpa.git branch? If so, we can have a > > single elpa.git branch where each package is represented by a suitable > > commit, right? For example, we can have a "stable" branch in > > elpa.git, where the last commit of each package corresponds to the > > latest stable version of that package. Is that possible? > > Yes, you could create a branch that merges all the bundled packages > (from their separate branches) together, > > However, if you then make changes in that merged branch (which we > definitely want to support), it is not simple to propagate them back to > the separate branches; you have to cherry-pick. I don't think we want to maintain the bundled packages inside the Emacs repository. IOW, the flow of changes should be unidirectional: from elpa.git to emacs.git, but not in the other direction.