From: the-maldridge <the-maldridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] How to progress with gcc and libatomic
Date: Sun, 06 Mar 2022 02:19:19 +0100 [thread overview]
Message-ID: <20220306011919.Y440cHriDnxVKSDF4Nh-1bo1qKJ6o2f3EY-O7_Jw3kM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35992@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 245 bytes --]
New comment by the-maldridge on void-packages repository
https://github.com/void-linux/void-packages/issues/35992#issuecomment-1059868182
Comment:
Sounds reasonable to me, has upstream provided a reason for the two patches to not be accepted?
next prev parent reply other threads:[~2022-03-06 1:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 12:54 [ISSUE] " leahneukirchen
2022-03-06 1:19 ` the-maldridge [this message]
2022-03-06 12:13 ` leahneukirchen
2022-06-27 2:16 ` github-actions
2022-09-26 2:15 ` github-actions
2023-01-12 21:55 ` Johnnynator
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=20220306011919.Y440cHriDnxVKSDF4Nh-1bo1qKJ6o2f3EY-O7_Jw3kM@z \
--to=the-maldridge@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).