emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Kaushal Modi <kaushal.modi@gmail.com>
To: Bastien Guerry <bzg@gnu.org>, Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
	Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Unique org version for dev builds? (Was: org -> org export ignores latex ..)
Date: Mon, 16 May 2016 15:31:44 +0000	[thread overview]
Message-ID: <CAFyQvY2WnnowSB5SD79b3uFCxnU1cen=bvEoUh_kmnBbrRpMNg@mail.gmail.com> (raw)
In-Reply-To: <87y47e7yid.fsf@saiph.selenimh>

[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]

Hi Bastien, Achim,

I have added you to this thread to get help on how to make it easy to
identify if the current version of org-mode is the dev build.

As of now, M-x org-version shows "Org-mode version 8.3.4 .." for both
master and maint build of org-mode. Would it be possible to have the
version show something like "Org-mode version 8.3.4-dev .." for master
branch builds?

That allows a quick visual confirmation if someone is using the dev or
stable build. Also it would be useful in creating version checking elisp
wrappers around not-yet-released org-mode code in personal configs.

Something like below would then be possible

(if (org-mode-dev-p)
    (progn
      ;; new style
      )
  (progn
    ;; old style
    ))

Thanks.


On Fri, May 13, 2016 at 11:45 AM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> Kaushal Modi <kaushal.modi@gmail.com> writes:
>
> > It would have been nice if the master branch built version showed a
> > different numerical version number than the one on the maint branch. Or
> > probably some prefix like dev/master? Nicolas?
>
> Deciding the next version number ahead of time isn't always right from
> the beginning of the branch. I guess a "dev" suffix should be enough.
>
> However, I don't know how to change the release tag, which is defined in
> a somewhat convoluted way. Bastien or Achim probably know how to do it.
>
> --

-- 
Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 2104 bytes --]

next prev parent reply	other threads:[~2016-05-16 15:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 16:57 Bug: org -> org export ignores latex blocks [8.3.4 (8.3.4-50-g83e373-elpaplus @ /home/andrea/.emacs.d/elpa/org-plus-contrib-20160509/)] Andrea
2016-05-12 18:53 ` John Hendy
2016-05-12 18:57   ` Kaushal Modi
2016-05-12 19:16     ` John Hendy
2016-05-12 19:24       ` Kaushal Modi
2016-05-12 19:27         ` John Hendy
2016-05-13 15:45         ` Nicolas Goaziou
2016-05-16 15:31           ` Kaushal Modi [this message]
2016-05-12 21:41       ` Andrea
2016-05-12 22:00         ` Kaushal Modi
2016-05-12 22:23           ` Andrea
2016-05-12 22:27             ` Kaushal Modi
2016-05-12 22:44               ` Andrea

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='CAFyQvY2WnnowSB5SD79b3uFCxnU1cen=bvEoUh_kmnBbrRpMNg@mail.gmail.com' \
    --to=kaushal.modi@gmail.com \
    --cc=Stromeko@nexgo.de \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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

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).