From: Jambunathan K <kjambunathan@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Version strings in lisp files?
Date: Sat, 21 Apr 2012 19:39:51 +0530 [thread overview]
Message-ID: <81bomlnplc.fsf@gmail.com> (raw)
In-Reply-To: <87ty0dxlwr.fsf@gnu.org> (Bastien's message of "Sat, 21 Apr 2012 15:19:16 +0200")
Bastien <bzg@gnu.org> writes:
> Jambunathan K <kjambunathan@gmail.com> writes:
>
>> (version-list-= (version-to-list "7.8.09")
>> (version-to-list "7.8.9"))
>>
>> To a human, 7.8.09 != 7.8.9. But to Emacs, they are just the same.
>
> Right. I will use 7.8.10 for the next version 7.9.1 for the first
> minor version after 7.9.
That's nice. If you still want to tag something as really minor, you
can go with 7.9.0.1, for example.
[CONTEXT SWITCH]
Btw, we can consider starting a etc/ORG-NEWS directory (much along the
lines of ERC-NEWS, GNUS-NEWS, MH-E-NEWS and NXML-NEWS)
We can mention the worthies since the last Emacs sync - ODT export for
example :-). (I can submit a patch once a ORG-NEWS file is created in
bzr repo) Another way to fill the file is to make a copy-pasta from
Changes.org.
If it is too much of a hassle, ORG-NEWS could start out empty or very
minimal. No doubt there is plenty of ORG-NEWS already for the next
Emacs-24.1+ releases.
This will necessitate a ORG-NEWS in Org's repo as well.
Jambunathan K.
next prev parent reply other threads:[~2012-04-21 14:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 11:27 Version strings in lisp files? Achim Gratz
2012-04-21 12:37 ` Jambunathan K
2012-04-21 13:19 ` Bastien
2012-04-21 14:09 ` Jambunathan K [this message]
2012-04-21 14:28 ` Bastien
2012-04-21 13:43 ` Eli Zaretskii
2012-04-21 14:11 ` Bastien
2012-04-21 14:14 ` Eli Zaretskii
2012-04-21 14:34 ` Jambunathan K
2012-04-21 14:48 ` Eli Zaretskii
2012-04-21 14:47 ` Achim Gratz
2012-04-21 19:40 ` Stefan Monnier
2012-04-21 19:54 ` Achim Gratz
2012-04-21 22:59 ` Bastien
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=81bomlnplc.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=bzg@gnu.org \
--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).