From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-devel@gnu.org
Subject: Re: Supporting multiline Package-Requires header
Date: Mon, 17 Aug 2015 20:45:00 +0200 [thread overview]
Message-ID: <87egj1pxeb.fsf@Rainer.invalid> (raw)
In-Reply-To: jwvfv3mabp6.fsf-monnier+emacs@gnu.org
Stefan Monnier writes:
> Last I checked, your GNU ELPA packages have "bogus" version numbers that
> don't look like "8.3.1".
So who's been messing with the scripts on ELPA that the latest Org
package got called "org-8.3.1" or was that just Rasmus' addition of the
version header? Besides the fact that this is the wrong version since
the packaged one is "8.3.1-56-g17a225-elpa", it nicely ensures that
nobody ever updates to it.
Really, whatever you don't like about the way the Org ELPA package is
created is probably fixable, but this is not the way to do it.
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:[~2015-08-17 18:45 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 11:12 Supporting multiline Package-Requires header Artur Malabarba
2015-08-10 11:42 ` Kaushal
2015-08-10 11:59 ` Artur Malabarba
2015-08-10 12:05 ` Phillip Lord
2015-08-10 12:28 ` Artur Malabarba
2015-08-10 12:51 ` Phillip Lord
2015-08-10 13:08 ` Artur Malabarba
2015-08-10 13:54 ` Bozhidar Batsov
2015-08-10 15:22 ` Artur Malabarba
2015-08-11 21:05 ` Phillip Lord
2015-08-11 21:48 ` Artur Malabarba
2015-08-12 5:34 ` Bozhidar Batsov
2015-08-12 14:09 ` Stefan Monnier
2015-08-12 14:23 ` Artur Malabarba
2015-08-12 17:18 ` Stefan Monnier
2015-08-12 20:10 ` Artur Malabarba
2015-08-13 18:13 ` Artur Malabarba
2015-08-13 20:44 ` Stefan Monnier
2015-08-13 22:37 ` Rasmus
2015-08-13 23:01 ` Artur Malabarba
2015-08-14 0:12 ` Rasmus
2015-08-14 1:42 ` Stefan Monnier
2015-08-17 18:45 ` Achim Gratz [this message]
2015-08-18 15:56 ` Stefan Monnier
2015-08-18 18:00 ` Achim Gratz
2015-08-19 17:14 ` Stefan Monnier
2015-08-23 6:33 ` Achim Gratz
2015-08-23 9:17 ` Artur Malabarba
2015-08-23 9:37 ` Achim Gratz
2015-08-23 12:03 ` Artur Malabarba
2015-08-23 22:17 ` Stefan Monnier
2015-08-23 22:12 ` Stefan Monnier
2015-08-23 23:32 ` Artur Malabarba
2015-08-23 22:16 ` Stefan Monnier
2015-08-24 6:56 ` Achim Gratz
2015-08-24 19:17 ` Stefan Monnier
2015-08-24 19:32 ` Achim Gratz
2015-08-24 22:51 ` Artur Malabarba
2015-08-25 5:44 ` Achim Gratz
2015-08-10 14:26 ` Thierry Volpiatto
2015-08-10 15:18 ` Artur Malabarba
2015-08-10 15:38 ` Thierry Volpiatto
2015-08-10 15:53 ` Artur Malabarba
2015-08-10 16:33 ` Thierry Volpiatto
2015-08-10 15:40 ` Nicolas Richard
2015-08-10 15:49 ` Artur Malabarba
2015-08-11 8:44 ` Nicolas Richard
2015-08-11 9:28 ` Artur Malabarba
2015-08-11 9:33 ` Nicolas Richard
2015-08-10 16:34 ` Thierry Volpiatto
2015-08-10 21:49 ` Phillip Lord
2015-08-11 9:24 ` Artur Malabarba
2015-08-10 22:05 ` Stefan Monnier
2015-08-11 8:56 ` Thierry Volpiatto
2015-08-11 15:55 ` Stefan Monnier
2015-08-10 22:01 ` Stefan Monnier
2015-08-11 9:29 ` Artur Malabarba
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=87egj1pxeb.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).