From: radiden <radiden@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pandoc: update to 2.11.4.
Date: Tue, 06 Apr 2021 11:35:05 +0200 [thread overview]
Message-ID: <20210406093505.3ue9pY_Ok4nWFYPR4irTj-cbOq6DsLz0VW_0DRY1fdw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30026@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
New comment by radiden on void-packages repository
https://github.com/void-linux/void-packages/pull/30026#issuecomment-813978858
Comment:
> Why 2.11 and not 2.13?
On the top of the template I read:
```
# Keep in sync with http://www.stackage.org/lts
```
Which when i clicked brought me to the lts-17.9 resolver. From that, I'm guessing it is preferred to use an LTS version.
next prev parent reply other threads:[~2021-04-06 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 22:41 [PR PATCH] " radiden
2021-04-05 23:33 ` abenson
2021-04-06 9:35 ` radiden [this message]
2021-04-11 3:51 ` [PR PATCH] [Merged]: " abenson
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=20210406093505.3ue9pY_Ok4nWFYPR4irTj-cbOq6DsLz0VW_0DRY1fdw@z \
--to=radiden@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).