From: zmudc <zmudc@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: tigervnc: update to 1.13.1, add service directory
Date: Mon, 31 Jul 2023 04:05:45 +0200 [thread overview]
Message-ID: <20230731020545.d66M0hPSThV4L0BQzQFWSG6BQTTPixjRJJZ7iLMHfuE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45307@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
New comment by zmudc on void-packages repository
https://github.com/void-linux/void-packages/pull/45307#issuecomment-1657297383
Comment:
The updated PR has been tested and is ready to be reviewed for the second round. I think it addresses all of the concerns of @classabbyamp.
Thanks.
Also, note that the e-mail address to which github sent messages for this PR does not match the e-mail address I put in the commit message. I haven't firgured out how to fix that yet. I wanted github to use the brchuckz@aol.com address, and I set my public address to that address and used that address in the commit message, but github for some reason sent the comments to my other email address associated with my github account: frchuckz@gmail.com. I think it is because there were more email settings I had to update. Hopefully it is fixed now. Sorry about that.
next prev parent reply other threads:[~2023-07-31 2:05 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 6:11 [PR PATCH] " zmudc
2023-07-29 16:21 ` [PR REVIEW] " classabbyamp
2023-07-29 16:21 ` classabbyamp
2023-07-29 16:21 ` classabbyamp
2023-07-29 16:21 ` classabbyamp
2023-07-29 16:21 ` classabbyamp
2023-07-29 16:21 ` classabbyamp
2023-07-29 16:21 ` classabbyamp
2023-07-29 16:21 ` classabbyamp
2023-07-29 16:46 ` zmudc
2023-07-29 16:56 ` zmudc
2023-07-29 16:59 ` zmudc
2023-07-29 17:01 ` zmudc
2023-07-29 17:09 ` [PR REVIEW] " zmudc
2023-07-29 17:15 ` zmudc
2023-07-29 17:17 ` zmudc
2023-07-29 17:20 ` zmudc
2023-07-30 19:27 ` [PR PATCH] [Updated] " zmudc
2023-07-30 19:57 ` zmudc
2023-07-30 22:39 ` zmudc
2023-07-30 22:48 ` zmudc
2023-07-30 22:48 ` zmudc
2023-07-30 23:31 ` [PR REVIEW] " zmudc
2023-07-30 23:32 ` zmudc
2023-07-30 23:33 ` zmudc
2023-07-30 23:34 ` zmudc
2023-07-30 23:39 ` zmudc
2023-07-30 23:46 ` zmudc
2023-07-31 2:05 ` zmudc [this message]
2023-07-31 2:38 ` [PR PATCH] [Updated] " zmudc
2023-07-31 2:49 ` zmudc
2023-07-31 3:43 ` [PR PATCH] [Updated] " zmudc
2023-08-01 0:07 ` zmudc
2023-08-01 0:10 ` zmudc
2023-08-07 15:16 ` zmudc
2023-08-11 2:48 ` zmudc
2023-08-11 2:56 ` zmudc
2023-08-17 19:33 ` [PR PATCH] [Updated] " zmudc
2023-08-17 19:46 ` ahesford
2023-08-17 19:56 ` [PR PATCH] [Updated] " zmudc
2023-08-17 20:00 ` zmudc
2023-08-17 20:00 ` [PR PATCH] [Closed]: " zmudc
2023-08-17 20:02 ` zmudc
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=20230731020545.d66M0hPSThV4L0BQzQFWSG6BQTTPixjRJJZ7iLMHfuE@z \
--to=zmudc@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).