From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: sheldon-0.7.0
Date: Thu, 13 Oct 2022 20:21:23 +0200 [thread overview]
Message-ID: <20221013182123.2XJTu4A7st9SjIaADR5_I2jrZFbAWh5pt5YszJTDkMc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38488@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 230 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/38488#issuecomment-1278003758
Comment:
yeah well not really, my PR is still open. Something similar has been merged though.
next prev parent reply other threads:[~2022-10-13 18:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 18:03 [PR PATCH] New package: sheldon-0.6.6 tranzystorek-io
2022-08-05 18:18 ` [PR PATCH] [Updated] " tranzystorek-io
2022-08-13 6:51 ` tranzystorek-io
2022-08-24 10:35 ` tranzystorek-io
2022-08-24 22:38 ` tranzystorek-io
2022-09-04 11:56 ` jcgruenhage
2022-09-04 11:59 ` tranzystorek-io
2022-09-04 21:53 ` jcgruenhage
2022-09-04 21:55 ` jcgruenhage
2022-10-13 14:15 ` [PR PATCH] [Updated] " tranzystorek-io
2022-10-13 14:39 ` [PR PATCH] [Updated] New package: sheldon-0.7.0 tranzystorek-io
2022-10-13 15:10 ` tranzystorek-io
2022-10-13 18:21 ` jcgruenhage [this message]
2022-11-02 8:47 ` [PR PATCH] [Updated] " tranzystorek-io
2023-02-01 2:07 ` New package: sheldon-0.7.1 github-actions
2023-02-01 15:22 ` [PR PATCH] [Updated] " tranzystorek-io
2023-02-26 16:56 ` tranzystorek-io
2023-02-26 19:33 ` tranzystorek-io
2023-03-05 13:13 ` jcgruenhage
2023-04-02 9:36 ` [PR PATCH] [Updated] " tranzystorek-io
2023-04-21 9:15 ` tranzystorek-io
2023-05-14 7:17 ` tranzystorek-io
2023-05-16 18:03 ` [PR PATCH] [Updated] New package: sheldon-0.7.2 tranzystorek-io
2023-06-09 22:39 ` [PR PATCH] [Updated] New package: sheldon-0.7.3 tranzystorek-io
2023-06-24 12:14 ` [PR PATCH] [Merged]: " Duncaen
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=20221013182123.2XJTu4A7st9SjIaADR5_I2jrZFbAWh5pt5YszJTDkMc@z \
--to=jcgruenhage@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).