public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Kolen Cheung
	<christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Interested in pre-built pandoc binary for Raspberry Pi?
Date: Thu, 19 Sep 2019 11:30:59 -0700	[thread overview]
Message-ID: <yh480kpnjwf89o.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <0261ce84-ce3e-4d0e-bc54-8ffc57426ed3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


I suspect many people will appreciate this, yes!

Kolen Cheung <christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> It seems to be easy to compile pandoc on the new Raspberry Pi 4. I uploaded 
> pandoc 2.7.3 compiled on RPi4 (32bit) in 
> https://github.com/ickc/pandoc-arm/releases . Let me know if you think it 
> is useful to continue to provide this.
>
> -- 
> 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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/0261ce84-ce3e-4d0e-bc54-8ffc57426ed3%40googlegroups.com.


  parent reply	other threads:[~2019-09-19 18:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 10:13 Kolen Cheung
     [not found] ` <0261ce84-ce3e-4d0e-bc54-8ffc57426ed3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-09-19 18:30   ` John MacFarlane [this message]
     [not found]     ` <yh480kpnjwf89o.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-20  7:45       ` mb21
     [not found]         ` <b6e39060-b59f-4a5d-a57e-ca757671439a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-11-25  5:08           ` Kolen Cheung

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=yh480kpnjwf89o.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=christian.kolen-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).