From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Andrea <agiugliano91@gmail.com>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: 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/)]
Date: Fri, 13 May 2016 17:45:14 +0200 [thread overview]
Message-ID: <87y47e7yid.fsf@saiph.selenimh> (raw)
In-Reply-To: <CAFyQvY1uPJgQ+ONKOVFLAUuW=M8tV2Qxyhq-GmxGn2h0eehctw@mail.gmail.com> (Kaushal Modi's message of "Thu, 12 May 2016 19:24:04 +0000")
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.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-05-13 15:55 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 [this message]
2016-05-16 15:31 ` Unique org version for dev builds? (Was: org -> org export ignores latex ..) Kaushal Modi
2016-05-12 21:41 ` 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 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=87y47e7yid.fsf@saiph.selenimh \
--to=mail@nicolasgoaziou.fr \
--cc=agiugliano91@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@gmail.com \
/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).