From: prez <prez@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] Move package requests elsewhere
Date: Wed, 20 Apr 2022 13:27:44 +0200 [thread overview]
Message-ID: <20220420112744.G82VcnTOTyU_IJ9aPea1GfLRKUCMK9ZAVwMnUc-UAq8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36700@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
New comment by prez on void-packages repository
https://github.com/void-linux/void-packages/issues/36700#issuecomment-1103823446
Comment:
>As it currently stands, there's no check (manual or automatic) in place to ensure requests actually get closed when the package is added. I wouldn't be surprised new package PRs are merged without the author realising there could be a request to close.
And how does your "solution" address this?
Strongly disagree with this. Having the requests as issues in the same repository is very convenient, and like Duncaen said, you can always use filters.
next prev parent reply other threads:[~2022-04-20 11:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 3:22 [ISSUE] " 0x5c
2022-04-17 10:00 ` mjyut
2022-04-17 16:34 ` mjyut
2022-04-17 16:46 ` Duncaen
2022-04-17 16:47 ` Duncaen
2022-04-17 16:47 ` Duncaen
2022-04-17 16:50 ` Duncaen
2022-04-17 17:02 ` mjyut
2022-04-17 17:26 ` mjyut
2022-04-20 0:25 ` 0x5c
2022-04-20 11:27 ` prez [this message]
2022-04-21 20:34 ` 0x5c
2022-04-21 20:36 ` Duncaen
2022-07-21 2:15 ` github-actions
2022-08-07 2:14 ` [ISSUE] [CLOSED] " github-actions
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=20220420112744.G82VcnTOTyU_IJ9aPea1GfLRKUCMK9ZAVwMnUc-UAq8@z \
--to=prez@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).