From: Kyle Meyer <firstname.lastname@example.org>
To: Bastien <email@example.com>, "Kévin Le Gouguec" <firstname.lastname@example.org>
Subject: Re: Release 9.3.8
Date: Wed, 09 Sep 2020 20:45:20 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
> Kévin Le Gouguec <firstname.lastname@example.org> writes:
>> Bastien <email@example.com> writes:
>>>> - During the development of 9.4, AFAICT, while the "Version:" comment in
>>>> org.el sayd "9.4-dev", the org-version variable matched the latest
>>>> tag, i.e. 9.3.x.
>>>> I therefore couldn't figure out a way to check for 9.4
>>> ... because 9.4 is not yet released - or am I missing something?
>> See Emacs's master branch for a counter-example: even though 28.1 is not
>> out yet, emacs-version says "28.0.50", so one can determine that they're
>> running on the master branch.
> Well, yes, but I find that confusing: "I'm using the 28.0.50 version,
> which looks like an officially released version, while it's not."
Can't you inspect the return value of org-git-version? (Though in my
view, distinguishing based on the functionality present with things like
fboundp, which you mention below, is typically a better approach, if
next prev parent reply other threads:[~2020-09-10 0:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 15:49 Release 9.3.8 Bastien
2020-09-07 17:23 ` Kévin Le Gouguec
2020-09-07 17:45 ` Bastien
2020-09-08 5:35 ` Kévin Le Gouguec
2020-09-09 8:17 ` Bastien
2020-09-10 0:45 ` Kyle Meyer [this message]
2020-09-10 6:32 ` Check for master branch from Elisp (was: Release 9.3.8) Kévin Le Gouguec
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).