From: Yin <zaxebo1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: approximate release date of 1.19.2.2
Date: Mon, 25 Sep 2017 06:51:58 -0700 (PDT) [thread overview]
Message-ID: <8e67ffb4-6d96-4d4b-b612-0c5b34e386dc@googlegroups.com> (raw)
In-Reply-To: <20170924161129.GA12601-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1572 bytes --]
Its a great news that pandoc 2.0 will be released "in next month itself",
we are all eagerly waiting for it with hands crossed.
Thanks a lot in advance for the 2.0. :-)
Yin
On Sunday, September 24, 2017 at 9:41:35 PM UTC+5:30, John MacFarlane wrote:
>
> 1.19.2.2 (3, 4) have all been released. They are basically
> just small tweaks of the build dependencies, and fixes for
> newer versions of ghc.
>
> All substantive fixes will be in pandoc 2.0, which I hope
> will be released before too much longer - maybe in the next
> month or so.
>
> +++ Yin [Sep 24 17 01:00 ]:
> > pandoc version 1.19.2.1 was released as far back as on 3rd feb 2017.
> > I see three development branches 1.19.2.2, 1.19.2.3, 1.19.2.4 at
> > https://github.com/jgm/pandoc/branches
> > When will be the 1.19.2.2 be released. any roadmap?
> >
> > (note: I am just curious due to fixing of the bug
> > https://github.com/jgm/pandoc/issues/3787#issuecomment-317883590 )
> > Yin
> >
>
>
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/8e67ffb4-6d96-4d4b-b612-0c5b34e386dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 3273 bytes --]
prev parent reply other threads:[~2017-09-25 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 8:00 Yin
[not found] ` <5ea60276-e9be-41e3-887e-cf7339668d44-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-24 16:11 ` John MACFARLANE
[not found] ` <20170924161129.GA12601-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2017-09-25 13:51 ` Yin [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8e67ffb4-6d96-4d4b-b612-0c5b34e386dc@googlegroups.com \
--to=zaxebo1-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).