From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: approximate release date of 1.19.2.2
Date: Sun, 24 Sep 2017 09:11:29 -0700 [thread overview]
Message-ID: <20170924161129.GA12601@protagoras.berkeley.edu> (raw)
In-Reply-To: <5ea60276-e9be-41e3-887e-cf7339668d44-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [3]https://groups.google.com/d/msgid/pandoc-discuss/5ea60276-e9be-41e3-
> 887e-cf7339668d44%40googlegroups.com.
> For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
> 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 3. https://groups.google.com/d/msgid/pandoc-discuss/5ea60276-e9be-41e3-887e-cf7339668d44-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 4. https://groups.google.com/d/optout
next prev parent reply other threads:[~2017-09-24 16:11 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 [this message]
[not found] ` <20170924161129.GA12601-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2017-09-25 13:51 ` Yin
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=20170924161129.GA12601@protagoras.berkeley.edu \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).