From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] enable discussions for void-packages
Date: Wed, 29 Mar 2023 00:26:03 +0200 [thread overview]
Message-ID: <20230328222603.xMP27uP74El2JLEx2VPLGlPyQme78r9Dq-lJYS-DsW8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43081@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 321 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/43081#issuecomment-1487682303
Comment:
> Also `Fixes #xxxx` wouldn't work I think.
as a stop-gap until github implements it, a workflow could be used to close discussions, assuming the api endpoints are there
next prev parent reply other threads:[~2023-03-28 22:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 20:56 [ISSUE] " classabbyamp
2023-03-28 21:29 ` Duncaen
2023-03-28 21:39 ` leahneukirchen
2023-03-28 22:12 ` ahesford
2023-03-28 22:26 ` classabbyamp [this message]
2023-06-27 2:08 ` github-actions
2023-06-28 5:18 ` [ISSUE] [CLOSED] " the-maldridge
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=20230328222603.xMP27uP74El2JLEx2VPLGlPyQme78r9Dq-lJYS-DsW8@z \
--to=classabbyamp@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).