From: tibequadorian <tibequadorian@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] Give stale PRs 2 weeks to show signs of life
Date: Tue, 22 Mar 2022 21:14:08 +0100 [thread overview]
Message-ID: <20220322201408.jCzoU8w3xjRc-6o3liEvbq0N5UmGo78Udz5Bcl5th2E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36253@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
New comment by tibequadorian on void-packages repository
https://github.com/void-linux/void-packages/issues/36253#issuecomment-1075594774
Comment:
I know the content doesn't disappear but the list of closed PRs (which is 40x bigger and growing) is usually not considered when searching for a useful PR to build upon. Not least because GitHub filters for open PRs automatically. I'd rather just mark them as inactive and keep them open as long as they are useful to others.
next prev parent reply other threads:[~2022-03-22 20:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 3:17 [ISSUE] " 0x5c
2022-03-21 3:25 ` subnut
2022-03-21 3:31 ` 0x5c
2022-03-22 17:58 ` classabbyamp
2022-03-22 18:04 ` tibequadorian
2022-03-22 19:59 ` 0x5c
2022-03-22 19:59 ` 0x5c
2022-03-22 20:14 ` tibequadorian [this message]
2022-03-22 21:38 ` 0x5c
2022-03-22 23:51 ` 0x5c
2022-04-11 1:39 ` 0x5c
2022-04-11 1:39 ` [ISSUE] [CLOSED] " 0x5c
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=20220322201408.jCzoU8w3xjRc-6o3liEvbq0N5UmGo78Udz5Bcl5th2E@z \
--to=tibequadorian@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).