unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: stephen_leake@stephe-leake.org, daniele@grinta.net,
	monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: decision on moving core packages to ELPA; also move to obsolete?
Date: Wed, 16 Dec 2020 17:33:27 +0200	[thread overview]
Message-ID: <83bletahq0.fsf@gnu.org> (raw)
In-Reply-To: <81776be3-2bfe-2d5c-6aae-6d905426e5cf@yandex.ru> (message from Dmitry Gutov on Tue, 15 Dec 2020 22:55:21 +0200)

> Cc: daniele@grinta.net, stephen_leake@stephe-leake.org, emacs-devel@gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Tue, 15 Dec 2020 22:55:21 +0200
> 
> Forgive me if that has already been suggested, but how about either:
> 
> - When making an Emacs X.YZ release, we require that every "external" 
> package has a tag emacs-xyz in its repository, and we pull in and 
> package that version.
> 
> - In the very same file in Emacs' tree that the repositories with 
> external packages will be listed, we also list the corresponding 
> revisions that will go into the upcoming release.
> 
> The latter is essentially the "git modules" model, which we can also 
> use.

I think, if the above suits us (see my other message in this thread),
we should indeed use "git submodule".

> One advantage it has is that the package author forgotten to push a 
> tag for some Emacs release, we're still covered.

You mean, advantage compared to using submodules?  If so, I don't
think I see how submodules are different in this regard.



  reply	other threads:[~2020-12-16 15:33 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14 19:59 decision on moving core packages to ELPA; also move to obsolete? Stephen Leake
2020-12-14 20:07 ` Eli Zaretskii
2020-12-14 23:40   ` Stefan Monnier
2020-12-15  5:06     ` Eli Zaretskii
2020-12-15  9:32       ` Daniele Nicolodi
2020-12-15 16:57         ` Eli Zaretskii
2020-12-15 17:03           ` Stefan Monnier
2020-12-15 17:30             ` Glenn Morris
2020-12-15 17:43               ` Glenn Morris
2020-12-15 17:54                 ` Glenn Morris
2020-12-15 19:50               ` Stefan Monnier
2020-12-15 18:28             ` Eli Zaretskii
2020-12-15 18:49               ` Stephen Leake
2020-12-15 18:53                 ` Stephen Leake
2020-12-15 19:13                   ` Eli Zaretskii
2020-12-15 19:54                     ` Stefan Monnier
2020-12-15 20:11                       ` Eli Zaretskii
2020-12-15 20:55                         ` Dmitry Gutov
2020-12-16 15:33                           ` Eli Zaretskii [this message]
2020-12-16 16:09                             ` Dmitry Gutov
2020-12-15 22:01                         ` Stefan Monnier
2020-12-16  3:13                           ` Tests in core depending on GNU ELPA packages (was: decision on moving core packages to ELPA; also move to obsolete?) Thomas Fitzsimmons
2020-12-16  3:24                             ` Tests in core depending on GNU ELPA packages Stefan Monnier
2021-02-19  1:09                               ` Thomas Fitzsimmons
2021-02-19  1:15                                 ` Stefan Monnier
2020-12-16 17:53                           ` decision on moving core packages to ELPA; also move to obsolete? Eli Zaretskii
2020-12-16 18:35                             ` Stefan Monnier
2020-12-16 19:23                               ` Eli Zaretskii
2020-12-16 20:01                                 ` Stefan Monnier
2020-12-16 20:05                                   ` Eli Zaretskii
2020-12-16 20:13                                     ` Stefan Monnier
2020-12-16 19:46                       ` Stephen Leake
2020-12-16 20:10                         ` Stefan Monnier
2020-12-16 19:21                     ` Stephen Leake
2020-12-16 19:56                       ` Eli Zaretskii
2020-12-15 19:57                 ` Stefan Monnier
2020-12-15 20:16                   ` Eli Zaretskii
2020-12-15 22:09                     ` Stefan Monnier
2020-12-16  8:29                       ` Michael Albinus
2020-12-16 14:20                         ` Stefan Monnier
2020-12-16 14:42                           ` Michael Albinus
2020-12-16  8:47                       ` Andrea Corallo via Emacs development discussions.
2020-12-16 17:56                       ` Eli Zaretskii
2020-12-16 18:46                         ` Stefan Monnier
2020-12-16 19:28                           ` Eli Zaretskii
2020-12-16 20:05                             ` Stefan Monnier
2020-12-15 18:33             ` Eli Zaretskii
2020-12-15 20:11               ` Stefan Monnier
2020-12-15 20:29                 ` Eli Zaretskii
2020-12-15 22:25                   ` Stefan Monnier
2020-12-16 17:59                     ` Eli Zaretskii
2020-12-16 18:50                       ` Stefan Monnier
2020-12-16 19:32                         ` Eli Zaretskii
2020-12-16 20:06                           ` Stefan Monnier
2020-12-16 20:19                             ` Eli Zaretskii
2020-12-16 21:03                               ` Stefan Monnier
2020-12-16 19:44                   ` Stephen Leake
2020-12-16 20:01                     ` Eli Zaretskii
2021-01-10 23:05                     ` ELPA notes, README Stephen Leake
2021-01-10 23:14                       ` Stefan Monnier
2020-12-15 14:05       ` decision on moving core packages to ELPA; also move to obsolete? Stefan Monnier
2020-12-15 17:04         ` Eli Zaretskii
2020-12-15 17:28           ` Stefan Monnier
2020-12-15  5:46   ` Lars Ingebrigtsen
2020-12-15 18:50     ` Stephen Leake
2021-01-07 17:33 ` Stephen Leake
2021-01-07 20:00   ` Stefan Monnier
2021-01-08 17:00     ` Stephen Leake

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83bletahq0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=daniele@grinta.net \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=stephen_leake@stephe-leake.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).