From: Gordon Pettey <petteyg359@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Massive Github PR Queue
Date: Fri, 11 Aug 2023 18:37:10 -0500 [thread overview]
Message-ID: <CAHY5Med1OG3q6rUtHnqnU1r_sf4aB5xTHWOhdjebnGciN5PCxA@mail.gmail.com> (raw)
In-Reply-To: <ad131963-afd8-04f7-5ddf-e84f0539892a@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
On Fri, Aug 11, 2023 at 11:11 AM Joonas Niilola <juippis@gentoo.org> wrote:
>
> Another big issue is as mjo pointed out, not everyone uses GH.
>
"Not using GitHub" is not an excuse for a PR to sit ignored when it has a
bug attachment. Anyone can view a PR anonymously and clone the remote from
the read-only https URL. There's no "using github" required for that beyond
clicking the link in the attached bug to see the PR and the remote
repository name. For the 202 "bug linked" (excluding "new package") PRs,
~50% are more than 6 months old. While that doesn't necessarily mean
they've been ignored (for the "not using GitHub" devs, the code could've
been merged that way without any interaction on the GH PR, then it would be
up to the submitter to close the PR), it still doesn't look great.
[-- Attachment #2: Type: text/html, Size: 1180 bytes --]
next prev parent reply other threads:[~2023-08-11 23:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 14:07 [gentoo-dev] Massive Github PR Queue orbea
2023-08-11 14:19 ` Michael Orlitzky
2023-08-11 14:46 ` orbea
2023-08-11 15:06 ` Michael Orlitzky
2023-08-11 16:10 ` Joonas Niilola
2023-08-11 16:54 ` Sam James
2023-08-11 18:09 ` Rich Freeman
2023-08-11 17:35 ` orbea
2023-08-12 1:18 ` Michael Orlitzky
2023-08-12 2:12 ` Mike Gilbert
2023-08-12 13:33 ` Haelwenn (lanodan) Monnier
2023-08-12 2:30 ` Michał Górny
2023-08-11 23:37 ` Gordon Pettey [this message]
2023-08-12 1:33 ` Michael Orlitzky
2023-08-12 14:05 ` orbea
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=CAHY5Med1OG3q6rUtHnqnU1r_sf4aB5xTHWOhdjebnGciN5PCxA@mail.gmail.com \
--to=petteyg359@gmail.com \
--cc=gentoo-dev@lists.gentoo.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