From: Jambunathan K <kjambunathan@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [CONCERN] Orgmode version string
Date: Fri, 29 Oct 2010 23:23:16 +0530 [thread overview]
Message-ID: <81pqusq41f.fsf@gmail.com> (raw)
In-Reply-To: <0854CA9A-5755-4E7B-99E6-D2E911D55FF7@gmail.com> (Carsten Dominik's message of "Fri, 29 Oct 2010 16:51:10 +0200")
Carsten
You haven't misunderstood my arguments at all.
>
> - do not use something like 7.02a, because the letter will defeat
> version number testing
> - from our most recent exchange I felt that you agree that
> 7.02 will behave correctly when compared with the
> version- functions. So I actually understood that
> you agreed with me.
I thought you would go with 7.20 :-) and I didn't see any problem with
that.
>
> The reason why I use 7.02 at all is just because I think it
> is pretty when one is expecting 2-digit release numbers.
> The release file numbers line up nicely in a directory listing.
> Things like this.
>
> Do you have the patience to summarize the arguments for me?
It is better to avoid a '0' prefix. If you build a org-7.02.tar and try
installing using the package manager, you would know what I mean.
> I will go with 7.3 for the next release if this is what is
> really needed.
It is improper for me to say what version you should use. I am careful
that I wouldn't step in to that territory.
All I can say is that C-h v version-to-list and C-h v
version-regexp-alist are your friends. There is a range of schemes
available and surely one such scheme will suit your tastes.
As for snapshot releases it is better rely on the YYYYMMDD scheme for
packaging. M-x org-version can continue to report git magic numbers in
the version string.
Jambunathan K.
next prev parent reply other threads:[~2010-10-29 17:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 12:40 [CONCERN] Orgmode version string Jambunathan K
2010-10-28 14:06 ` Bastien
2010-10-28 16:27 ` Jambunathan K
2010-10-28 18:16 ` Jambunathan K
2010-10-28 21:57 ` Carsten Dominik
2010-10-29 1:36 ` Jambunathan K
2010-10-29 13:06 ` Jambunathan K
2010-10-29 14:51 ` Carsten Dominik
2010-10-29 17:53 ` Jambunathan K [this message]
2010-10-29 14:53 ` 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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81pqusq41f.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=carsten.dominik@gmail.com \
--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).