From: zlice <zlice@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qt6-pdf: split from webengine, build for 32 bit archs.
Date: Thu, 14 Dec 2023 19:20:53 +0100 [thread overview]
Message-ID: <20231214182053.llR_tejPCNIQYE9gQBtsNMJukn8KNbExPM-TL-8oHUU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47679@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 206 bytes --]
New comment by zlice on void-packages repository
https://github.com/void-linux/void-packages/pull/47679#issuecomment-1856362056
Comment:
Ah got it. as long as it's staying that way ill rebase ffmpeg. thx
prev parent reply other threads:[~2023-12-14 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 16:14 [PR PATCH] " sgn
2023-12-10 16:18 ` [PR PATCH] [Updated] " sgn
2023-12-11 11:52 ` sgn
2023-12-11 11:53 ` sgn
2023-12-11 15:00 ` sgn
2023-12-12 6:45 ` sgn
2023-12-12 6:46 ` [PR PATCH] [Merged]: " sgn
2023-12-14 17:16 ` zlice
2023-12-14 18:18 ` Johnnynator
2023-12-14 18:20 ` zlice [this message]
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=20231214182053.llR_tejPCNIQYE9gQBtsNMJukn8KNbExPM-TL-8oHUU@z \
--to=zlice@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).