Github messages for voidlinux
 help / color / mirror / Atom feed
From: 0x5c <0x5c@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 20:59:14 +0100	[thread overview]
Message-ID: <20220322195914.BCsDdGkd-XyzOLrplVzu_zRTfZrvuxTmBDjcmdAUDEg@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: 647 bytes --]

New comment by 0x5c on void-packages repository

https://github.com/void-linux/void-packages/issues/36253#issuecomment-1075582712

Comment:
@tibequadorian Closing PR also doesn't block anyone from discussing those PRs, nor does it make the PR's content disappear. It all remains there for anyone else to build upon, just without the immense strain on the backlog. If anything, an open PR can discourage others from making new and updated PRs for the same things. And as Abby said, the label doesn't have to be removed from PRs once they are closed for inactivity, and the whole process involves sending a comment explaining why the PR got closed.

  parent reply	other threads:[~2022-03-22 19:59 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 [this message]
2022-03-22 19:59 ` 0x5c
2022-03-22 20:14 ` tibequadorian
2022-03-22 21:38 ` 0x5c
2022-03-22 23:51 ` 0x5c
2022-04-11  1:39 ` [ISSUE] [CLOSED] " 0x5c
2022-04-11  1:39 ` 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=20220322195914.BCsDdGkd-XyzOLrplVzu_zRTfZrvuxTmBDjcmdAUDEg@z \
    --to=0x5c@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).