From: Bastien <bzg@gnu.org>
To: Jay Kerns <gjkernsysu@gmail.com>
Cc: Memnon Anon <gegendosenfleisch@googlemail.com>, emacs-orgmode@gnu.org
Subject: Re: Release 8.0
Date: Mon, 22 Apr 2013 19:17:19 +0200 [thread overview]
Message-ID: <87sj2ipjs0.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CAFiLVrYwKH1a56xLN4rV6p9hgSeWsV8BMr28Uud5=Sz+SGQZ8Q@mail.gmail.com> (Jay Kerns's message of "Mon, 22 Apr 2013 12:56:42 -0400")
Hi Jay,
Jay Kerns <gjkernsysu@gmail.com> writes:
> On Sun, Apr 21, 2013 at 9:25 AM, Bastien <bzg@gnu.org> wrote:
>> Hi Memnon,
>>
>> Memnon Anon <gegendosenfleisch@googlemail.com> writes:
>
> [ snip ]
>
> Quick question: is it true, now that Org 8.0 has been released, that
> the engine which publishes Worg is now Org 8.0, too?
No, not yet.
> In other words, is it now safe to publish to Worg all of that stuff
> which was written compatible with the new exporter, without breaking
> Worg in the process?
No. Someone needs to carefully check he can exports his local clone
of worg.git with the new exporter, fix the wrong syntax, then commit
it. This surely deserves a public branch of Worg, which people can
hack together.
--
Bastien
next prev parent reply other threads:[~2013-04-22 17:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 16:41 Release 8.0 Bastien
2013-04-18 16:58 ` Jambunathan K
2013-04-18 17:37 ` Bastien
2013-04-18 18:06 ` Jambunathan K
2013-04-18 17:15 ` Anthony Lander
2013-04-18 17:28 ` Appeal to donors (Re: Release 8.0) Jambunathan K
2013-04-19 15:42 ` OAppeal " Wes Hardaker
2013-04-19 16:38 ` Russell Adams
2013-04-18 17:41 ` Release 8.0 Neuwirth Erich
2013-04-18 18:01 ` Achim Gratz
2013-05-09 7:55 ` Neuwirth Erich
2013-04-18 17:43 ` François Pinard
2013-04-18 17:57 ` Glyn Millington
2013-04-18 18:24 ` Jambunathan K
2013-04-18 18:00 ` John Hendy
2013-04-18 18:10 ` Aaron Ecay
2013-04-18 18:18 ` Jambunathan K
2013-04-18 18:22 ` Bastien
2013-04-18 19:09 ` Jambunathan K
2013-04-18 19:16 ` Jambunathan K
2013-04-18 19:28 ` Billy O'Connor
2013-04-18 19:50 ` Jambunathan K
2013-04-18 20:15 ` Bastien
2013-04-18 20:20 ` Glyn Millington
2013-04-18 18:17 ` Rasmus
2013-04-18 19:28 ` Samuel Wales
2013-04-18 22:05 ` Carsten Dominik
2013-04-19 4:53 ` Brian van den Broek
2013-04-20 8:15 ` Xiao-Yong Jin
2013-04-19 0:20 ` Bernt Hansen
2013-04-19 6:58 ` Christian Moe
2013-04-19 8:02 ` Stefan Vollmar
2013-04-21 12:07 ` Memnon Anon
2013-04-21 13:25 ` Bastien
2013-04-22 16:56 ` Jay Kerns
2013-04-22 17:17 ` Bastien [this message]
2013-04-22 18:32 ` Carsten Dominik
2013-04-22 19:46 ` John Hendy
2013-04-22 20:06 ` Carsten Dominik
2013-04-22 20:17 ` Thorsten Jolitz
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=87sj2ipjs0.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=gegendosenfleisch@googlemail.com \
--cc=gjkernsysu@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).