Github messages for voidlinux
 help / color / mirror / Atom feed
From: VuiMuich <VuiMuich@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: leftwm-0.2.8
Date: Sat, 04 Dec 2021 07:23:21 +0100	[thread overview]
Message-ID: <20211204062321.sz0_i2kW6oVQHaoVSas5zX9yhbbmVISDRoFHeNTca5w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31657@inbox.vuxu.org>

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

New comment by VuiMuich on void-packages repository

https://github.com/void-linux/void-packages/pull/31657#issuecomment-985977720

Comment:
> @uncomfyhalomacro I'm running `leftwm` built from git-HEAD on NetBSD right now. You will need Rust >= 1.56 to build 0.2.10, Void is still on Rust-1.53

As of now we haven't pushed the 2021 Edition Upgrade for `leftwm`.
Do you see realistic chances of Void bumping their Rust version in close future? We might consider holding this back as we currently are not depending on any of the new optimizations or features.

  parent reply	other threads:[~2021-12-04  6:23 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25 21:56 [PR PATCH] New package: leftwm-0.2.7 ReneganRonin
2021-06-25 22:33 ` [PR PATCH] [Updated] " ReneganRonin
2021-06-25 22:55 ` ReneganRonin
2021-06-25 22:57 ` ReneganRonin
2021-06-25 23:15 ` ReneganRonin
2021-06-26  1:42 ` ReneganRonin
2021-06-26 11:49 ` [PR REVIEW] " Johnnynator
2021-06-26 11:52 ` Johnnynator
2021-06-26 12:29 ` [PR PATCH] [Updated] " ReneganRonin
2021-06-26 12:31 ` ReneganRonin
2021-06-26 12:33 ` [PR REVIEW] " ReneganRonin
2021-06-26 12:33 ` ReneganRonin
2021-06-26 13:22 ` ericonr
2021-06-26 13:22 ` ericonr
2021-06-26 13:30 ` ReneganRonin
2021-06-26 13:31 ` [PR PATCH] [Updated] " ReneganRonin
2021-06-26 13:54 ` Johnnynator
2021-06-26 14:00 ` ReneganRonin
2021-06-26 14:13 ` Johnnynator
2021-06-26 14:29 ` [PR PATCH] [Updated] " ReneganRonin
2021-06-26 14:31 ` ReneganRonin
2021-06-26 14:31 ` ReneganRonin
2021-06-26 21:50 ` ericonr
2021-06-26 22:59 ` ReneganRonin
2021-06-26 23:05 ` ReneganRonin
2021-06-27  1:23 ` ReneganRonin
2021-06-27  1:23 ` ReneganRonin
2021-06-27  1:26 ` ReneganRonin
2021-06-27  6:39 ` ReneganRonin
2021-06-27 22:38 ` [PR PATCH] [Updated] " ReneganRonin
2021-06-27 22:49 ` ReneganRonin
2021-06-27 22:54 ` ReneganRonin
2021-06-28  2:00 ` ericonr
2021-06-28 14:21 ` ReneganRonin
2021-06-28 14:22 ` ReneganRonin
2021-06-29  2:02 ` [PR PATCH] [Updated] " ReneganRonin
2021-07-07 14:05 ` [PR PATCH] [Updated] New package: leftwm-0.2.8 ReneganRonin
2021-07-07 14:06 ` ReneganRonin
2021-07-07 22:25 ` ReneganRonin
2021-07-08  0:19 ` ReneganRonin
2021-07-08  2:14 ` ReneganRonin
2021-07-09  9:58 ` ReneganRonin
2021-11-20 18:25 ` VuiMuich
2021-11-21  4:16 ` [PR REVIEW] " ericonr
2021-11-21  4:41 ` [PR PATCH] [Updated] " uncomfyhalomacro
2021-11-21  5:11 ` uncomfyhalomacro
2021-11-22 10:13 ` uncomfyhalomacro
2021-12-03  5:46 ` 0323pin
2021-12-04  5:49 ` uncomfyhalomacro
2021-12-04  6:13 ` 0323pin
2021-12-04  6:14 ` 0323pin
2021-12-04  6:22 ` VuiMuich
2021-12-04  6:23 ` VuiMuich [this message]
2021-12-04  6:24 ` VuiMuich
2022-01-11  5:05 ` [PR PATCH] [Updated] " uncomfyhalomacro
2022-01-11  5:14 ` New package: leftwm-0.2.11 uncomfyhalomacro
2022-01-12 14:02 ` [PR PATCH] [Updated] " uncomfyhalomacro
2022-01-12 16:31 ` uncomfyhalomacro
2022-01-12 16:33 ` uncomfyhalomacro
2022-01-12 16:54 ` uncomfyhalomacro
2022-01-13 11:35 ` [PR REVIEW] " Johnnynator
2022-01-13 11:35 ` Johnnynator
2022-01-13 14:35 ` [PR PATCH] [Updated] " uncomfyhalomacro
2022-01-13 14:55 ` uncomfyhalomacro
2022-01-13 15:07 ` uncomfyhalomacro
2022-01-13 15:10 ` [PR PATCH] [Updated] " uncomfyhalomacro
2022-01-14  0:17 ` uncomfyhalomacro
2022-01-14  0:31 ` uncomfyhalomacro
2022-01-14 14:11 ` 0323pin
2022-01-15 14:26 ` [PR PATCH] [Updated] " Johnnynator
2022-01-15 14:28 ` Johnnynator
2022-01-15 14:28 ` [PR PATCH] [Merged]: " Johnnynator
2022-04-26  5:31 ` 0323pin
2022-04-26 11:11 ` uncomfyhalomacro

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=20211204062321.sz0_i2kW6oVQHaoVSas5zX9yhbbmVISDRoFHeNTca5w@z \
    --to=vuimuich@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).