From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: lilypond: update to 2.19.84
Date: Sun, 09 Feb 2020 19:03:28 +0100 [thread overview]
Message-ID: <20200209180328.NwLi90P4lzEDallch33ypzgyhkdvwgKVGpM_n84h_pM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18965@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 416 bytes --]
There's a merged pull request on the void-packages repository
lilypond: update to 2.19.84
https://github.com/void-linux/void-packages/pull/18965
Description:
Compiled for and tested on x86_64, x86_64-musl, i686, armv7l; no problems.
Packages also built sucessfully for aarch64 and armv6l.
Due to its ten thousand files lilypond-doc will exceed maximum log length, but I didn’t encounter any problem locally.
parent reply other threads:[~2020-02-09 18:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18965@inbox.vuxu.org>]
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=20200209180328.NwLi90P4lzEDallch33ypzgyhkdvwgKVGpM_n84h_pM@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).