From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: GNU ELPA package for CC-mode
Date: Fri, 24 Aug 2018 11:43:53 +0300 [thread overview]
Message-ID: <83lg8w9mt2.fsf@gnu.org> (raw)
In-Reply-To: <jwv36v4u4ha.fsf-monnier+gmane.emacs.devel@gnu.org> (message from Stefan Monnier on Thu, 23 Aug 2018 18:17:22 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Thu, 23 Aug 2018 18:17:22 -0400
>
> > and is THE version of CC Mode. The proposed VERSION: header is not
> > a part of CC Mode, it is part of ELPA, recording the number of the
> > ELPA release only.
>
> The "Version:" header could just as well be THE version.
For packages which already have some "version" string somewhere, why
cannot we teach package.el to look for them, when it doesn't find the
"Version:" header? I think this should be easy to implement (we could
ask the package maintainers to add something or use some standard
format, if what we already have is not enough), and should leave
everyone happy. Right?
next prev parent reply other threads:[~2018-08-24 8:43 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-19 13:24 GNU ELPA package for CC-mode Stefan Monnier
2018-08-19 20:49 ` Alan Mackenzie
2018-08-19 23:45 ` Stefan Monnier
2018-08-20 8:24 ` Jostein Kjønigsen
2018-08-20 14:06 ` Stefan Monnier
2018-08-20 17:58 ` Jostein Kjønigsen
2018-08-21 13:30 ` Stefan Monnier
2018-08-21 16:20 ` Alan Mackenzie
2018-08-23 5:25 ` Stefan Monnier
2018-08-23 21:34 ` Alan Mackenzie
2018-08-23 22:17 ` Stefan Monnier
2018-08-24 8:43 ` Eli Zaretskii [this message]
2018-08-24 11:56 ` Michael Albinus
2018-08-24 22:21 ` Stefan Monnier
2018-08-25 8:43 ` Tramp as ELPA package (was: GNU ELPA package for CC-mode) Michael Albinus
2018-08-25 18:04 ` Tramp as ELPA package Stefan Monnier
2018-08-25 21:04 ` Stefan Monnier
2018-08-26 6:39 ` Andreas Schwab
2018-08-26 10:48 ` Michael Albinus
2018-08-26 11:09 ` Michael Albinus
2018-08-26 15:21 ` Stefan Monnier
2018-08-26 18:04 ` Michael Albinus
2018-08-26 18:27 ` Eli Zaretskii
2018-08-26 18:34 ` Michael Albinus
2018-08-26 19:03 ` Eli Zaretskii
2018-08-27 7:12 ` Michael Albinus
2018-08-27 13:33 ` Stefan Monnier
2018-08-27 13:41 ` Michael Albinus
2018-08-27 13:44 ` Stefan Monnier
2018-08-27 15:22 ` Michael Albinus
2018-08-27 15:09 ` Eli Zaretskii
2018-08-27 15:21 ` Michael Albinus
2018-08-26 15:30 ` Tom Tromey
2018-08-26 16:26 ` Stefan Monnier
2018-08-26 17:46 ` Michael Albinus
2019-04-04 12:41 ` Michael Albinus
2019-04-04 15:48 ` Stefan Monnier
2019-04-04 16:07 ` Michael Albinus
2019-04-05 14:43 ` Michael Albinus
2019-04-05 15:07 ` Dmitry Gutov
2019-04-05 16:19 ` Michael Albinus
2019-04-16 7:53 ` Steinar Bang
2019-04-05 18:14 ` Stephen Leake
2019-04-05 18:20 ` Stephen Leake
2019-04-05 22:18 ` Michael Albinus
2019-04-07 0:17 ` Stephen Leake
2019-04-07 7:41 ` Michael Albinus
2019-04-06 12:42 ` Stefan Monnier
2019-04-08 12:37 ` Michael Albinus
2019-04-08 13:07 ` Stefan Monnier
2019-04-08 13:31 ` Michael Albinus
2019-04-08 16:43 ` Stefan Monnier
2019-05-20 13:05 ` Michael Albinus
2019-06-30 19:20 ` Michael Albinus
2019-04-05 18:55 ` Achim Gratz
2019-04-06 22:25 ` GNU ELPA and package.el (was: Tramp as ELPA package) Stefan Monnier
2019-04-07 7:17 ` GNU ELPA and package.el Achim Gratz
2019-04-07 14:07 ` Stefan Monnier
2019-04-07 17:37 ` Achim Gratz
2019-04-07 20:31 ` Stefan Monnier
2019-04-08 17:55 ` Achim Gratz
2019-04-08 19:01 ` Stefan Monnier
2019-04-08 20:24 ` Achim Gratz
2019-04-09 1:39 ` Stefan Monnier
2018-08-25 19:15 ` GNU ELPA package for CC-mode Clément Pit-Claudel
2018-08-25 20:17 ` Stefan Monnier
2018-08-25 21:17 ` Tom Tromey
2018-08-25 23:28 ` Kyle Andrews
2018-08-24 15:48 ` Stefan Monnier
2018-08-24 19:21 ` Eli Zaretskii
2018-08-24 22:17 ` Stefan Monnier
2018-08-25 7:02 ` Eli Zaretskii
2018-08-25 8:51 ` Alan Mackenzie
2018-08-25 10:15 ` Michael Albinus
2018-08-25 18:07 ` Stefan Monnier
2018-08-25 18:27 ` Eli Zaretskii
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=83lg8w9mt2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).