From: Glenn Morris <rgm@gnu.org>
To: Leo Liu <sdl.web@gmail.com>
Cc: chad <yandros@MIT.EDU>, 14338@debbugs.gnu.org
Subject: bug#14338: 24.3.50; ELPA package ack fails to install
Date: Fri, 03 May 2013 12:01:23 -0400 [thread overview]
Message-ID: <9ghaikvyr0.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m1wqrgmr5k.fsf@gmail.com> (Leo Liu's message of "Fri, 03 May 2013 15:57:59 +0800")
Leo Liu wrote:
> What should be done here to get it in sync?
Maybe use a version that is not zero padded.
Is 1.01 supposed to be the same as 1.1, or not?
> BTW, increment the version number is an annoyance. I wonder if people
> feel the same way too?
I have no opinion. The motivation is in packages/README:
This cron job only creates a new package when the "version" (as
specified in the foo-pkg.el or in the "Version:" header) of a
package is modified. This means that you can safely work on the next
version here without worrying about the unstable code making it to
GNU ELPA, and simply update the "version" when you want to release
the new code.
Seems sensible. Surely there needs to be some way to prevent every
change going live immediately?
next prev parent reply other threads:[~2013-05-03 16:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 2:39 bug#14338: 24.3.50; ELPA package ack fails to install chad
2013-05-03 7:49 ` Glenn Morris
2013-05-03 7:57 ` Leo Liu
2013-05-03 16:01 ` Glenn Morris [this message]
2013-05-03 16:04 ` Glenn Morris
2013-05-03 20:54 ` Leo Liu
2013-05-04 18:34 ` Glenn Morris
2013-05-04 18:56 ` Glenn Morris
2013-05-05 2:36 ` Leo Liu
2013-05-06 0:20 ` Glenn Morris
2013-05-06 1:54 ` Leo Liu
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=9ghaikvyr0.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=14338@debbugs.gnu.org \
--cc=sdl.web@gmail.com \
--cc=yandros@MIT.EDU \
/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).