From: alekseyt <alekseyt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: cross-x86_64-w64-mingw32: update to 7.0.0
Date: Sat, 21 Mar 2020 00:23:38 +0100 [thread overview]
Message-ID: <20200320232338.IeCjcANqSKYPJa1X37WL48dqQbkSKfF5OvFNrlK3tzE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16891@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
New comment by alekseyt on void-packages repository
https://github.com/void-linux/void-packages/pull/16891#issuecomment-601951004
Comment:
I've updated PR for GCC 9.3.0, some changes overlap with master, but nothing should conflict, i've also rebased it on newer master.
Other changes:
* MPFR is synced with `gcc/template` (4.0.2)
* Added tar to `hostmakedepends` - this was already added in master, now conflict with this branch is also resolved
prev parent reply other threads:[~2020-03-20 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16891@inbox.vuxu.org>
2020-03-20 23:21 ` alekseyt
2020-03-20 23:22 ` alekseyt
2020-03-20 23:22 ` alekseyt
2020-03-20 23:23 ` alekseyt
2020-03-20 23:23 ` alekseyt [this message]
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=20200320232338.IeCjcANqSKYPJa1X37WL48dqQbkSKfF5OvFNrlK3tzE@z \
--to=alekseyt@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).