Github messages for voidlinux
 help / color / mirror / Atom feed
From: OliveThePuffin <OliveThePuffin@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zig: update to 0.12.0.
Date: Sun, 21 Apr 2024 17:59:38 +0200	[thread overview]
Message-ID: <20240421155938.32D7B25223@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49935@inbox.vuxu.org>

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

New comment by OliveThePuffin on void-packages repository

https://github.com/void-linux/void-packages/pull/49935#issuecomment-2068104591

Comment:
Oh, I see what you mean now.

So 
river, waylock, ncdu2, zls, and linuxwave (templates that use zig-build)
all must build in this repo before merging. Makes sense.

I'll try to bump them now and see, but due to the breaking nature of early zig, this may have to wait a while.

  parent reply	other threads:[~2024-04-21 15:59 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-20 16:14 [PR PATCH] " OliveThePuffin
2024-04-20 16:16 ` [PR PATCH] [Updated] " OliveThePuffin
2024-04-20 16:25 ` OliveThePuffin
2024-04-20 16:27 ` OliveThePuffin
2024-04-20 16:34 ` [PR REVIEW] " OliveThePuffin
2024-04-20 18:23 ` dkwo
2024-04-20 23:54 ` OliveThePuffin
2024-04-21  8:21 ` icp1994
2024-04-21 15:59 ` OliveThePuffin [this message]
2024-04-21 19:13 ` tranzystorekk
2024-04-22  2:39 ` OliveThePuffin
2024-05-03 12:41 ` realcharmer
2024-05-03 16:48 ` OliveThePuffin
2024-05-03 16:50 ` OliveThePuffin
2024-05-03 19:10 ` [PR PATCH] [Updated] " OliveThePuffin
2024-05-05 17:35 ` Luciogi
2024-05-07 15:05 ` [PR PATCH] [Closed]: " OliveThePuffin
2024-05-07 15:05 ` [PR PATCH] [Updated] " OliveThePuffin
2024-05-07 15:11 ` OliveThePuffin
2024-05-07 15:48 ` OliveThePuffin
2024-05-07 16:00 ` tranzystorekk
2024-05-20 18:30 ` dkwo
2024-05-20 18:32 ` dkwo
2024-05-20 18:42 ` dkwo
2024-05-20 18:44 ` tranzystorekk
2024-05-20 18:46 ` dkwo
2024-05-20 20:14 ` tranzystorekk
2024-05-20 22:04 ` realcharmer
2024-05-22  2:23 ` jason1987d
2024-05-23  0:36 ` [PR PATCH] [Updated] " OliveThePuffin
2024-05-23  0:43 ` OliveThePuffin
2024-05-23  0:52 ` [PR PATCH] [Updated] " OliveThePuffin
2024-05-23  0:53 ` OliveThePuffin
2024-05-23  1:20 ` OliveThePuffin
2024-05-23  7:34 ` tranzystorekk
2024-05-23  7:36 ` tranzystorekk
2024-05-23  7:48 ` tranzystorekk
2024-05-23  8:48 ` tranzystorekk
2024-05-23 11:13 ` OutOfContainment
2024-05-23 13:26 ` dkwo
2024-05-25 14:56 ` icp1994
2024-05-25 16:10 ` tranzystorekk
2024-05-25 18:23 ` tranzystorekk

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=20240421155938.32D7B25223@inbox.vuxu.org \
    --to=olivethepuffin@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).