From: Paul Simmons <mbatranch@gmail.com>
To: development@lists.ipfire.org
Subject: Re: (low priority) comment about "patchwork"
Date: Fri, 24 Jan 2025 10:20:48 -0600 [thread overview]
Message-ID: <6131b7e9-e698-4c08-83fd-dd1b3698383c@gmail.com> (raw)
In-Reply-To: <CB0C1D8F-F5CD-493F-8A69-BA10C5EACDA1@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1599 bytes --]
On 1/24/25 07:55, Michael Tremer wrote:
> Hello Paul,
>
> Thanks for your curiosity, but things are not as bad as it sounds.
>
> Yes, there are loads of patches that are sort of abandoned, but that does not mean that there was any work wasted or that we have a huge backlog.
>
> There are probably some patches that were never intended to be merge - as a request for comments; some patches have probably been modified when merged so Patchwork might have failed to pick up the changes and that is why the patch remains “unmerged" on there; and there might have been patches that were once submitted, changes were required and the submitter never came back. It happens.
>
> There is probably a lot more stuff somewhere else that has not even made it onto the list.
>
> What is sparking your curiosity?
>
> -Michael
>
>> On 22 Jan 2025, at 18:16, Paul Simmons <mbatranch(a)gmail.com> wrote:
>>
>> I notice that "https://patchwork.ipfire.org/project/ipfire/list/" with selections "State = Action Required" and "Archived = No" has grown to 1230+ patches, many of which are very old (pre- 2024, and pre- Core191).
>> Is this intentional? Please don't interrupt your development flows to investigate... I'm only curious.
>> Many thanks,
>> P
Hello, Michael. Thanks for the reply!
I'm just "hyphenated" (is the term "anal-retentive" hyphenated?), and
wondered if patchwork was having difficulties :)
I'll go on about my business, "fret no more", and "endeavor to persevere".
I give thanks to "all y'all" for your efforts!
P
PS: Core190 update was very smooth!
prev parent reply other threads:[~2025-01-24 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0460e6b4-d6d4-4dce-a0c2-531ed9da62cb@gmail.com>
2025-01-24 13:55 ` Michael Tremer
2025-01-24 16:20 ` Paul Simmons [this message]
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=6131b7e9-e698-4c08-83fd-dd1b3698383c@gmail.com \
--to=mbatranch@gmail.com \
--cc=development@lists.ipfire.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