From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-devel@gnu.org
Cc: emacs-orgmode@gnu.org
Subject: Re: org-export raises stringp nil error
Date: Fri, 08 Mar 2013 17:34:42 +0100 [thread overview]
Message-ID: <87li9xu9y5.fsf@Rainer.invalid> (raw)
In-Reply-To: 83li9yyyul.fsf@gnu.org
Eli Zaretskii writes:
> That would certainly mean more problems for users to set them up with
> a particular version of Emacs, because there's no longer a clear way
> of getting the version of package X that correspond to Emacs version
> N.M.
As long as ELPA is in Git, that's absolutely no problem. The exact
version of the package that's going into an Emacs release is tagged with
that version. Emacs could even pull packages using these tags from ELPA
if the user first decided to install the latest version and then wants
to go back to the "built-in" package version.
And release branches would be the way to handle code freezes.
In any case, doing the built-in packages this way (or something similar)
takes a lot of unecessary churn and merges out of the release process
and I would think that would be a clear advantage to everyone involved.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2013-03-08 16:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ip539io1.fsf@nautilus.nautilus>
2013-03-07 21:14 ` org-export raises stringp nil error Glenn Morris
2013-03-07 22:38 ` Bastien
2013-03-08 1:36 ` Glenn Morris
2013-03-08 6:40 ` Bastien
2013-03-08 7:16 ` Leo Liu
2013-03-08 7:37 ` Bastien
2013-03-08 7:44 ` Leo Liu
2013-03-08 7:56 ` Xue Fuqiao
2013-03-08 8:28 ` Eli Zaretskii
2013-03-08 9:15 ` joakim
2013-03-08 9:17 ` Bastien
2013-03-08 9:19 ` Bastien
2013-03-08 9:25 ` Dmitry Gutov
2013-03-08 10:23 ` Eli Zaretskii
2013-03-08 11:18 ` Dmitry Gutov
2013-03-08 14:06 ` Eli Zaretskii
2013-03-08 21:00 ` Dmitry Gutov
2013-03-08 16:34 ` Achim Gratz [this message]
2013-03-08 19:48 ` Eli Zaretskii
2013-03-08 9:55 ` Stephen J. Turnbull
2013-03-08 10:15 ` Eli Zaretskii
2013-03-08 11:12 ` Dmitry Gutov
2013-03-08 14:21 ` Xue Fuqiao
2013-03-08 15:42 ` Bastien
2013-03-08 16:29 ` Nick Dokos
2013-03-08 16:38 ` Jambunathan K
2013-03-08 17:09 ` Bastien
2013-03-08 17:41 ` Nick Dokos
2013-03-08 18:01 ` Jambunathan K
2013-03-08 18:05 ` Nick Dokos
2013-03-08 19:40 ` Achim Gratz
2013-03-08 16:39 ` Bastien
2013-03-08 22:37 ` Xue Fuqiao
2013-03-08 7:47 ` Xue Fuqiao
2013-03-08 7:53 ` Bastien
2013-03-08 8:27 ` Stephen J. Turnbull
2013-03-08 8:58 ` Eli Zaretskii
2013-03-08 9:56 ` Stephen J. Turnbull
2013-03-08 8:30 ` Eli Zaretskii
2013-03-08 9:12 ` Bastien
2013-03-08 8:20 ` Stephen J. Turnbull
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87li9xu9y5.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-devel@gnu.org \
--cc=emacs-orgmode@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/org-mode.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).