From: Kolen Cheung <christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Status of pandoc-templates?
Date: Sat, 6 Oct 2018 19:58:08 -0700 (PDT) [thread overview]
Message-ID: <c9abc1a6-bfcf-4418-a5e4-1b271f69646f@googlegroups.com> (raw)
In-Reply-To: <m2sh1lru22.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1788 bytes --]
Is the change from submodules to subtree force you to start
pandoc-templates over? If so, I still thinks that leaving the old ones
around just to not having those 631 orphans would be better. I also deleted
my fork thinking it is no longer of use. Now knowing that it is still there
I should have talking a diff. somehow to scavenge something from it.
e.g. instead of deleting pandoc-templates and replacing it with a new one
of the same name, keeping pandoc-templates and may be having a new one like
pandoc-templates2. This way one can take a simple git diff between their
fork and your master and see how can one migrate to the new repo.
On Thursday, October 4, 2018 at 7:44:52 PM UTC-7, John MacFarlane wrote:
>
> Kolen Cheung <christi...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <javascript:>> writes:
>
> https://github.com/jgm/pandoc-templates does exist!
> But it is not a descendent of the old repo by that
> name.
>
> There were some changes. First we moved from
> submodules to a subtree. Now it's just a completely
> separate repository that tracks updates to the
> templates. (I update it on each pandoc release.) The
> canonical locations for the templates is now
> jgm/pandoc.
>
>
--
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/c9abc1a6-bfcf-4418-a5e4-1b271f69646f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 3068 bytes --]
next prev parent reply other threads:[~2018-10-07 2:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 1:36 Kolen Cheung
[not found] ` <70c082c6-8546-4ff0-b3c6-52c4b0b07c44-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-10-05 2:44 ` John MacFarlane
[not found] ` <m2sh1lru22.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2018-10-07 2:58 ` Kolen Cheung [this message]
[not found] ` <c9abc1a6-bfcf-4418-a5e4-1b271f69646f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-10-07 17:51 ` John MacFarlane
2018-10-07 22:53 ` Ka Hei Kolen Cheung
[not found] ` <m2ftxhmyql.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2018-10-07 23:03 ` 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=c9abc1a6-bfcf-4418-a5e4-1b271f69646f@googlegroups.com \
--to=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).