Github messages for voidlinux
 help / color / mirror / Atom feed
From: Bnyro <Bnyro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: go: update to 1.21.0.
Date: Sat, 12 Aug 2023 23:27:25 +0200	[thread overview]
Message-ID: <20230812212725.9Nd7ZZ8WdQkSvvO1ZjM0nB9Tn0Gu08o4DR2brIqiyXw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45525@inbox.vuxu.org>

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

New comment by Bnyro on void-packages repository

https://github.com/void-linux/void-packages/pull/45525#issuecomment-1676106049

Comment:
I don't think all the packages should be rev-bumped, since that would block all builders for multiple days. @mhmdanas rather proposed that you compile all the packages on your local machine in the background or over night to see if all of them still build fine.

  parent reply	other threads:[~2023-08-12 21:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 18:10 [PR PATCH] " g4s8
2023-08-10 18:24 ` g4s8
2023-08-11 11:54 ` mhmdanas
2023-08-12 15:42 ` [PR PATCH] [Updated] " g4s8
2023-08-12 15:47 ` g4s8
2023-08-12 16:33 ` g4s8
2023-08-12 21:15 ` g4s8
2023-08-12 21:27 ` Bnyro [this message]
2023-08-13  8:03 ` paper42
2023-08-14 15:39 ` [PR PATCH] [Updated] " g4s8
2023-08-14 15:42 ` g4s8
2023-08-14 16:01 ` mhmdanas
2023-08-14 21:11 ` [PR PATCH] [Updated] " g4s8
2023-08-21  6:18 ` g4s8
2023-08-22  7:28 ` g4s8
2023-08-22  7:29 ` g4s8
2023-08-23  8:13 ` [PR PATCH] [Updated] " g4s8
2023-08-23 21:33 ` [PR PATCH] [Closed]: " the-maldridge
2023-12-02 21:58 ` dkwo
2023-12-02 22:01 ` dkwo
2023-12-07 10:22 ` g4s8
2023-12-07 15:01 ` dkwo

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=20230812212725.9Nd7ZZ8WdQkSvvO1ZjM0nB9Tn0Gu08o4DR2brIqiyXw@z \
    --to=bnyro@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).