From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: turnstile-0.1.8
Date: Tue, 16 Jan 2024 20:42:58 +0100 [thread overview]
Message-ID: <20240116194258.9ED5027B88@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44676@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 415 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/pull/44676#issuecomment-1894399522
Comment:
i understand you'd want to wait for turnstile itself, but why not merge at least the pam-base change?
or even gdm, lightdm, polkit, if the absence of turnstile does not create any issue for them.
this would allow to not rebase this pr at every change of pam, libcrypto, etc.
next prev parent reply other threads:[~2024-01-16 19:42 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 9:12 [PR PATCH] New package: turnstile-0.1.4 classabbyamp
2023-06-28 20:45 ` dkwo
2023-06-28 21:36 ` classabbyamp
2023-07-04 8:36 ` [PR PATCH] [Updated] " classabbyamp
2023-07-04 8:40 ` classabbyamp
2023-07-04 8:43 ` classabbyamp
2023-07-04 8:45 ` classabbyamp
2023-07-04 8:59 ` classabbyamp
2023-07-04 9:00 ` classabbyamp
2023-07-04 9:44 ` New package: turnstile-0.1.5 classabbyamp
2023-07-04 9:58 ` classabbyamp
2023-07-09 22:52 ` [PR PATCH] [Updated] " classabbyamp
2023-07-10 14:03 ` junkminerman
2023-07-10 16:37 ` classabbyamp
2023-07-10 16:55 ` classabbyamp
2023-07-10 17:59 ` junkminerman
2023-07-10 18:04 ` classabbyamp
2023-07-10 21:36 ` junkminerman
2023-07-10 21:44 ` classabbyamp
2023-07-11 9:01 ` junkminerman
2023-07-12 3:06 ` [PR PATCH] [Updated] " classabbyamp
2023-07-13 23:29 ` New package: turnstile-0.1.6 junkminerman
2023-07-25 17:27 ` [PR PATCH] [Updated] " classabbyamp
2023-09-08 10:47 ` classabbyamp
2023-09-08 10:56 ` classabbyamp
2023-09-08 11:04 ` [PR PATCH] [Closed]: New package: turnstile-0.1.8 classabbyamp
2023-09-08 11:05 ` classabbyamp
2023-09-08 12:58 ` dkwo
2023-09-08 14:13 ` classabbyamp
2023-09-09 22:21 ` [PR PATCH] [Updated] " classabbyamp
2023-09-09 22:23 ` classabbyamp
2023-09-10 0:02 ` classabbyamp
2023-09-11 8:19 ` dkwo
2023-09-12 22:55 ` [PR PATCH] [Updated] " classabbyamp
2023-09-12 23:09 ` classabbyamp
2023-09-26 17:44 ` dkwo
2023-09-26 18:04 ` dkwo
2023-09-26 18:06 ` classabbyamp
2023-09-26 18:09 ` classabbyamp
2023-09-26 20:15 ` dkwo
2023-09-26 21:15 ` dkwo
2023-09-26 21:16 ` dkwo
2023-09-26 21:25 ` classabbyamp
2023-09-26 21:40 ` dkwo
2023-09-26 21:41 ` dkwo
2023-12-26 1:45 ` github-actions
2023-12-26 17:52 ` [PR PATCH] [Updated] " classabbyamp
2023-12-26 17:54 ` classabbyamp
2023-12-26 19:05 ` dkwo
2023-12-26 19:24 ` classabbyamp
2024-01-16 19:42 ` dkwo [this message]
2024-01-16 20:08 ` classabbyamp
2024-03-22 20:31 ` [PR PATCH] [Updated] " classabbyamp
2024-03-22 21:02 ` classabbyamp
2024-03-22 21:11 ` [PR PATCH] [Merged]: " classabbyamp
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=20240116194258.9ED5027B88@inbox.vuxu.org \
--to=dkwo@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).