Github messages for voidlinux
 help / color / mirror / Atom feed
From: fvalasiad <fvalasiad@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: wine: update to 9.0
Date: Thu, 18 Jan 2024 15:38:40 +0100	[thread overview]
Message-ID: <20240118143840.3418122DB0@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48249@inbox.vuxu.org>

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

New comment by fvalasiad on void-packages repository

https://github.com/void-linux/void-packages/pull/48249#issuecomment-1898604630

Comment:
@AlexKurisu Hmmm indeed there is no performance penalty to pay between using the old WoW64 with 32bit binaries and using the new one with only 64bit binaries. So wine on musl so far was not able to run windows 32bit apps at all? This means that the musl experience is also improved, god I love the new wine release!

I upvote, it's a good idea, what do you think @Hoshpak.

  parent reply	other threads:[~2024-01-18 14:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 15:10 [PR PATCH] " fvalasiad
2024-01-17 15:14 ` [PR PATCH] [Updated] " fvalasiad
2024-01-17 15:17 ` fvalasiad
2024-01-17 17:20 ` [PR REVIEW] " Hoshpak
2024-01-17 17:20 ` Hoshpak
2024-01-17 17:29 ` [PR PATCH] [Updated] " fvalasiad
2024-01-17 17:30 ` [PR REVIEW] " fvalasiad
2024-01-17 17:31 ` fvalasiad
2024-01-17 17:34 ` Hoshpak
2024-01-17 17:42 ` fvalasiad
2024-01-18 13:12 ` AlexKurisu
2024-01-18 14:38 ` fvalasiad [this message]
2024-01-18 14:40 ` fvalasiad
2024-01-18 14:58 ` AlexKurisu
2024-01-18 17:03 ` Hoshpak
2024-01-18 17:03 ` Hoshpak
2024-01-18 17:03 ` Hoshpak
2024-01-18 17:33 ` [PR PATCH] [Updated] " fvalasiad
2024-01-18 17:36 ` fvalasiad
2024-01-18 18:04 ` fvalasiad
2024-01-19 23:14 ` [PR PATCH] [Updated] " fvalasiad
2024-01-19 23:41 ` fvalasiad
2024-01-20  8:57 ` [PR PATCH] [Merged]: " Hoshpak

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=20240118143840.3418122DB0@inbox.vuxu.org \
    --to=fvalasiad@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).