From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Denis Maier
<denis.maier.lists-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Dev version and latest binary at the same time
Date: Mon, 14 Sep 2020 09:23:29 -0700 [thread overview]
Message-ID: <m2imcgnx8e.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <80c2e758-19f5-cb58-a4df-9b2df8a66b50-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
The easiest thing to do would be to rename the dev version
binary as pandoc-dev or something.
Denis Maier <denis.maier.lists-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org> writes:
> Hi,
>
> is there a recommended way for having the dev version and the latest
> official version installed at the same time? How can you still use the
> official version in a production environment while tinkering with the
> dev version?
>
> Best,
> Denis
>
> --
> 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/80c2e758-19f5-cb58-a4df-9b2df8a66b50%40mailbox.org.
next prev parent reply other threads:[~2020-09-14 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 8:10 Denis Maier
[not found] ` <80c2e758-19f5-cb58-a4df-9b2df8a66b50-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2020-09-14 9:02 ` Albert Krewinkel
[not found] ` <87r1r4n338.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2020-09-14 19:48 ` Denis Maier
2020-09-14 16:23 ` John MacFarlane [this message]
[not found] ` <m2imcgnx8e.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-09-14 19:46 ` Denis Maier
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=m2imcgnx8e.fsf@MacBook-Pro.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=denis.maier.lists-cl+VPiYnx/1AfugRpC6u6w@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).