From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-devel@gnu.org
Subject: Re: Adding ELPA to Emacs core
Date: Mon, 12 Mar 2018 20:16:42 +0100 [thread overview]
Message-ID: <87ina1ayud.fsf@Rainer.invalid> (raw)
In-Reply-To: 87tvtmqnh5.fsf@russet.org.uk
Phillip Lord writes:
> One thing that does worry me is that it means Emacs source as references
> to ELPA git. If Emacs (or ELPA) ever needs to move VCS, it's going to
> require some significant hackery.
Well, if you replace those SHA you were previously talking about with
tags, then the required hackery gets significantly reduced. And no, I
don't think that EMACS needs to be able to reference any SHA directly
since ELPA is well enough under control to be able to place tags where
you need them, maybe even of the form emacs-x.y.z or similar so it
becomes clear which of these are in use where. Naming the tags
explicitly to indicate Emacs' use of them would certainly help any
maintainer who would want to backport important patches to a branch that
older Emacsen can use.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
next prev parent reply other threads:[~2018-03-12 19:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-10 12:13 Adding ELPA to Emacs core Phillip Lord
2018-03-10 18:59 ` Eli Zaretskii
2018-03-10 20:44 ` Phillip Lord
2018-03-11 3:56 ` Stefan Monnier
2018-03-11 22:03 ` Phillip Lord
2018-03-12 19:16 ` Achim Gratz [this message]
2018-03-12 21:11 ` Phillip Lord
2018-03-13 0:53 ` Stefan Monnier
2018-03-13 17:00 ` Phillip Lord
2018-03-13 21:16 ` Stefan Monnier
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=87ina1ayud.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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 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).