Github messages for voidlinux
 help / color / mirror / Atom feed
From: SpidFightFR <SpidFightFR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: meson: update to version 1.4.0.
Date: Mon, 01 Apr 2024 16:06:12 +0200	[thread overview]
Message-ID: <20240401140612.5996C24AAB@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49288@inbox.vuxu.org>

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

New comment by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/pull/49288#issuecomment-2029812819

Comment:
Either we leave the current build of budgie-desktop-view as such (unchanged), knowing that we can't build it again untill upstream fix their work. In that case, the PR is ready.

Or we go with the "disabling error checking" thing. Not a huge fan of it, not gonna lie.

Also can we re-run a `check build` please ? It seems those are broken cuz i made the last commit right when wlroots was updated...

  parent reply	other threads:[~2024-04-01 14:06 UTC|newest]

Thread overview: 100+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14 11:46 [PR PATCH] " SpidFightFR
2024-03-14 11:53 ` SpidFightFR
2024-03-14 11:53 ` SpidFightFR
2024-03-15 22:47 ` SpidFightFR
2024-03-16 12:08 ` SpidFightFR
2024-03-16 12:21 ` SpidFightFR
2024-03-16 12:49 ` SpidFightFR
2024-03-17 11:03 ` SpidFightFR
2024-03-23 17:16 ` SpidFightFR
2024-03-24 20:56 ` [PR PATCH] [Updated] " SpidFightFR
2024-03-24 21:01 ` SpidFightFR
2024-03-24 21:16 ` [PR PATCH] [Updated] " SpidFightFR
2024-03-24 21:19 ` SpidFightFR
2024-03-24 21:31 ` [PR PATCH] [Updated] " SpidFightFR
2024-03-24 22:03 ` SpidFightFR
2024-03-25 20:37 ` [PR PATCH] [Updated] " SpidFightFR
2024-03-25 20:38 ` SpidFightFR
2024-03-25 20:40 ` SpidFightFR
2024-03-25 21:00 ` SpidFightFR
2024-03-25 21:00 ` [PR PATCH] [Updated] " SpidFightFR
2024-04-01 12:06 ` SpidFightFR
2024-04-01 13:51 ` meator
2024-04-01 14:03 ` SpidFightFR
2024-04-01 14:06 ` SpidFightFR [this message]
2024-04-01 14:10 ` meator
2024-04-01 14:14 ` [PR PATCH] [Updated] " SpidFightFR
2024-04-01 14:15 ` SpidFightFR
2024-04-01 15:21 ` meator
2024-04-01 15:24 ` eli-schwartz
2024-04-01 17:09 ` [PR PATCH] [Updated] " leahneukirchen
2024-04-01 17:11 ` SpidFightFR
2024-04-01 17:22 ` SpidFightFR
2024-04-01 17:33 ` [PR PATCH] [Updated] " SpidFightFR
2024-04-01 17:35 ` [PR REVIEW] " meator
2024-04-01 17:38 ` meator
2024-04-01 17:40 ` [PR PATCH] [Updated] " SpidFightFR
2024-04-01 17:40 ` [PR REVIEW] " SpidFightFR
2024-04-01 17:45 ` ahesford
2024-04-01 17:45 ` [PR PATCH] [Updated] " SpidFightFR
2024-04-01 17:46 ` [PR REVIEW] " meator
2024-04-01 17:47 ` [PR PATCH] [Updated] " SpidFightFR
2024-04-01 17:47 ` [PR REVIEW] " SpidFightFR
2024-04-01 17:48 ` SpidFightFR
2024-04-01 17:50 ` SpidFightFR
2024-04-01 18:06 ` [PR PATCH] [Updated] " SpidFightFR
2024-04-01 18:39 ` SpidFightFR
2024-04-01 18:57 ` SpidFightFR
2024-04-01 19:36 ` [PR REVIEW] " meator
2024-04-01 19:53 ` SpidFightFR
2024-04-01 19:56 ` [PR PATCH] [Updated] " SpidFightFR
2024-04-01 20:29 ` SpidFightFR
2024-04-07 23:35 ` ahesford
2024-04-08 19:29 ` [PR PATCH] [Updated] " SpidFightFR
2024-04-08 19:29 ` SpidFightFR
2024-04-08 19:30 ` SpidFightFR
2024-04-08 19:36 ` SpidFightFR
2024-04-08 20:12 ` SpidFightFR
2024-04-08 20:26 ` SpidFightFR
2024-04-08 20:27 ` SpidFightFR
2024-04-08 20:32 ` SpidFightFR
2024-04-08 20:36 ` SpidFightFR
2024-04-08 20:57 ` SpidFightFR
2024-04-08 20:58 ` [PR PATCH] [Updated] " SpidFightFR
2024-04-08 20:59 ` SpidFightFR
2024-04-09  5:09 ` SpidFightFR
2024-04-09  9:56 ` meator
2024-04-09 19:38 ` SpidFightFR
2024-04-10  9:21 ` [PR PATCH] [Updated] " SpidFightFR
2024-04-10  9:25 ` SpidFightFR
2024-04-10  9:36 ` SpidFightFR
2024-04-10  9:40 ` SpidFightFR
2024-04-10 10:11 ` SpidFightFR
2024-04-10 10:58 ` leahneukirchen
2024-04-10 12:46 ` SpidFightFR
2024-04-10 12:51 ` leahneukirchen
2024-04-10 12:58 ` eli-schwartz
2024-04-10 13:53 ` [PR PATCH] [Updated] " SpidFightFR
2024-04-13 19:10 ` SpidFightFR
2024-04-13 20:14 ` meator
2024-04-13 20:26 ` SpidFightFR
2024-04-13 20:27 ` meator
2024-04-13 20:32 ` SpidFightFR
2024-04-13 20:33 ` SpidFightFR
2024-04-13 20:41 ` SpidFightFR
2024-04-13 20:41 ` SpidFightFR
2024-04-13 20:42 ` SpidFightFR
2024-04-16 17:30 ` SpidFightFR
2024-04-16 17:31 ` SpidFightFR
2024-04-16 17:41 ` meator
2024-04-16 17:52 ` SpidFightFR
2024-04-21 14:50 ` [PR PATCH] [Updated] " SpidFightFR
2024-04-21 16:23 ` [PR REVIEW] " meator
2024-04-21 16:42 ` SpidFightFR
2024-04-21 16:55 ` [PR PATCH] [Updated] " SpidFightFR
2024-04-21 16:55 ` [PR REVIEW] " SpidFightFR
2024-04-21 17:13 ` eli-schwartz
2024-04-21 17:14 ` eli-schwartz
2024-04-21 17:45 ` SpidFightFR
2024-05-06 21:15 ` SpidFightFR
2024-05-07 19:13 ` [PR PATCH] [Merged]: " ahesford

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=20240401140612.5996C24AAB@inbox.vuxu.org \
    --to=spidfightfr@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).