Github messages for voidlinux
 help / color / mirror / Atom feed
From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: gcc: update to 13.2.0.
Date: Mon, 29 Jan 2024 00:43:36 +0100	[thread overview]
Message-ID: <20240128234336.9D0A62212A@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45500@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]

There's a closed pull request on the void-packages repository

gcc: update to 13.2.0.
https://github.com/void-linux/void-packages/pull/45500

Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
[ci skip]
#### Testing the changes
- I tested the changes in this PR: **briefly**

You can test the ISOs here: https://drive.google.com/drive/u/0/folders/1y5dkzI9R60eDjRA4mVYBdnn9e9PDGwNt

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


  parent reply	other threads:[~2024-01-28 23:43 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09  0:09 [PR PATCH] " oreo639
2023-08-26 21:48 ` leahneukirchen
2023-09-10 22:36 ` [PR REVIEW] " tornaria
2023-09-10 22:39 ` tornaria
2023-09-11  0:51 ` [PR REVIEW] " oreo639
2023-09-11 12:57 ` leahneukirchen
2023-09-11 15:51 ` oreo639
2023-12-07 17:53 ` metaleap
2023-12-07 18:54 ` oreo639
2023-12-07 18:54 ` oreo639
2023-12-07 18:54 ` oreo639
2023-12-07 18:55 ` oreo639
2023-12-07 18:55 ` oreo639
2023-12-26 21:54 ` oreo639
2023-12-26 22:10 ` [PR PATCH] [Updated] " oreo639
2023-12-27  4:15 ` oreo639
2023-12-27  4:16 ` oreo639
2023-12-27  4:17 ` oreo639
2023-12-27  8:51 ` [PR REVIEW] " averyterrel
2023-12-27  9:05 ` [PR PATCH] [Updated] " oreo639
2023-12-27  9:05 ` [PR REVIEW] " oreo639
2023-12-27 10:56 ` oreo639
2023-12-28  2:51 ` simvux
2023-12-28  3:21 ` oreo639
2023-12-28  3:21 ` oreo639
2023-12-28  3:21 ` oreo639
2023-12-28  3:22 ` oreo639
2023-12-28  3:23 ` oreo639
2023-12-28  3:30 ` [PR PATCH] [Updated] " oreo639
2023-12-28  3:32 ` oreo639
2023-12-29  1:27 ` [PR PATCH] [Updated] " oreo639
2024-01-10 16:12 ` dataCobra
2024-01-11  0:45 ` 22h49
2024-01-16 14:39 ` [PR PATCH] [Updated] " oreo639
2024-01-16 14:40 ` oreo639
2024-01-17 18:21 ` Calandracas606
2024-01-17 18:48 ` Calandracas606
2024-01-17 23:07 ` oreo639
2024-01-17 23:31 ` oreo639
2024-01-18  7:43 ` [PR PATCH] [Updated] " oreo639
2024-01-19  1:46 ` oreo639
2024-01-19  1:47 ` oreo639
2024-01-19  1:47 ` oreo639
2024-01-22  4:44 ` [PR PATCH] [Updated] " oreo639
2024-01-22  5:44 ` oreo639
2024-01-22  5:56 ` oreo639
2024-01-22 21:41 ` oreo639
2024-01-22 21:46 ` oreo639
2024-01-22 21:55 ` oreo639
2024-01-22 21:56 ` oreo639
2024-01-24 21:09 ` oreo639
2024-01-25 14:00 ` leahneukirchen
2024-01-27  2:30 ` [PR PATCH] [Updated] " oreo639
2024-01-27  9:27 ` oreo639
2024-01-27 22:34 ` oreo639
2024-01-28  1:40 ` oreo639
2024-01-28  5:27 ` oreo639
2024-01-28 23:43 ` oreo639 [this message]
2024-01-28 23:43 ` oreo639

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=20240128234336.9D0A62212A@inbox.vuxu.org \
    --to=oreo639@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).