From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: trouble exporting just one subtree while using babel and R code blocks--spoke too soon
Date: Fri, 08 Mar 2013 17:51:12 +0100 [thread overview]
Message-ID: <87haklu96n.fsf@Rainer.invalid> (raw)
In-Reply-To: 87d2va72dh.fsf@bzg.ath.cx
Bastien writes:
>> Bastien, I think it would make sense to clear up this confusion by
>> tagging 8dd2bfc291 with version 7.9.9 or 8.0-pre or something like that
>> (must be an annotated tag, of course). That'll help to easier determine
>> who's using the new and the old exporter.
>
> I used 8.0-pre -- thanks for the suggestion!
Thanks, but you tagged a different commit. The commit I named is the
one that moved the new exporter into core which I consider an important
milestone. I suggest to add two extra annotated tags to account
correctly (in the way version-to-list numbers things) for the history
leading up to the 8.0 release:
8dd2bfc291 release_8.0-alpha (move the new exporter into core)
ee3b3eb421 release_8.0-beta (remove /contrib/oldexp/)
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
next prev parent reply other threads:[~2013-03-08 16:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 21:10 trouble exporting just one subtree while using babel and R code blocks Christopher W. Ryan
2013-02-18 21:22 ` John Hendy
2013-03-06 19:33 ` Christopher W. Ryan
2013-03-06 21:28 ` John Hendy
2013-03-06 19:51 ` trouble exporting just one subtree while using babel and R code blocks--spoke too soon Christopher W. Ryan
2013-03-07 8:42 ` Eric S Fraga
2013-03-07 13:13 ` Christopher W Ryan
2013-03-07 14:36 ` Eric S Fraga
2013-03-07 17:55 ` Achim Gratz
2013-03-08 7:54 ` Bastien
2013-03-08 16:51 ` Achim Gratz [this message]
2013-03-08 17:25 ` Bastien
2013-03-08 19:48 ` Achim Gratz
2013-03-09 9:26 ` Bastien
2013-03-11 13:47 ` Christopher W. Ryan
2013-03-07 15:00 ` John Hendy
2013-03-07 15:54 ` Christopher W Ryan
2013-03-07 16:12 ` John Hendy
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=87haklu96n.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).