From: shnaps <shnaps@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: Logseq-0.9.17
Date: Fri, 12 Apr 2024 02:43:03 +0200 [thread overview]
Message-ID: <20240412004303.8B4C021473@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44337@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 414 bytes --]
New comment by shnaps on void-packages repository
https://github.com/void-linux/void-packages/pull/44337#issuecomment-2050772508
Comment:
> Yes, I'd like the update please. I don't want to use the Flatpak logseq
Maybe one of the maintainers could open this PR again. The branch itself is up to date and could be used for PR at any moment. @oreo639 @cinerea0 pinging you just in case, maybe you could help us.
prev parent reply other threads:[~2024-04-12 0:43 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 19:36 [PR PATCH] New package: Logseq-0.9.8 shnaps
2023-06-10 7:29 ` [PR PATCH] [Updated] " shnaps
2023-06-10 7:31 ` shnaps
2023-06-11 10:41 ` unrealjo
2023-06-11 11:17 ` classabbyamp
2023-06-11 16:16 ` unrealjo
2023-06-11 16:31 ` classabbyamp
2023-06-11 22:21 ` unrealjo
2023-06-11 22:25 ` [PR REVIEW] " classabbyamp
2023-06-11 22:25 ` classabbyamp
2023-06-12 17:09 ` shnaps
2023-06-12 17:14 ` shnaps
2023-06-12 19:00 ` classabbyamp
2023-06-12 21:50 ` shnaps
2023-06-19 17:39 ` [PR PATCH] [Updated] [WIP] " shnaps
2023-06-19 18:05 ` [PR REVIEW] [WIP] New package: Logseq-0.9.9 shnaps
2023-06-19 20:06 ` [PR PATCH] [Updated] " shnaps
2023-06-19 20:08 ` shnaps
2023-06-19 20:16 ` shnaps
2023-06-19 20:44 ` [PR PATCH] [Updated] [WIP] New package: Logseq-0.9.8 shnaps
2023-06-19 20:47 ` shnaps
2023-06-20 0:20 ` [PR PATCH] [Updated] " shnaps
2023-06-20 0:23 ` shnaps
2023-06-26 1:42 ` shnaps
2023-08-10 2:52 ` shnaps
2023-08-10 2:53 ` shnaps
2023-08-10 2:55 ` shnaps
2023-08-10 2:57 ` shnaps
2023-08-13 21:01 ` unrealjo
2023-08-13 21:01 ` unrealjo
2023-08-27 4:49 ` [PR PATCH] [Updated] " shnaps
2023-08-27 8:13 ` shnaps
2023-08-27 8:16 ` [PR PATCH] [Updated] New package: Logseq-0.9.15 shnaps
2023-08-27 8:19 ` shnaps
2023-08-27 8:38 ` [PR PATCH] [Updated] " shnaps
2023-09-06 18:04 ` shnaps
2023-09-06 18:07 ` [PR PATCH] [Updated] New package: Logseq-0.9.16 shnaps
2023-09-07 21:33 ` shnaps
2023-10-16 15:32 ` [PR PATCH] [Updated] New package: Logseq-0.9.17 shnaps
2024-01-15 1:48 ` github-actions
2024-01-30 1:44 ` [PR PATCH] [Closed]: " github-actions
2024-03-23 10:19 ` gontcharovd
2024-03-26 23:27 ` shnaps
2024-04-06 12:12 ` gontcharovd
2024-04-12 0:43 ` shnaps [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=20240412004303.8B4C021473@inbox.vuxu.org \
--to=shnaps@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).