From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] List of trivial old patches
Date: Sun, 07 May 2023 07:17:13 +0300 [thread overview]
Message-ID: <877ctkaf3h.fsf@tarshish> (raw)
In-Reply-To: <20230506151601.GA252090@scaer>
Hi Yann,
On Sat, May 06 2023, Yann E. MORIN wrote:
> On 2023-05-05 08:17 +0300, Baruch Siach via buildroot spake thusly:
>> Here is a list of over month old patchwork entries that look like
>> trivial version bumps, or upstream backports.
>> There are a lot more. So if you find this list useful, I'll dig up more
>> patches.
>
> I blindly applied the patches, on the assumption you did actually review
> them before adding them to the list, which was neither too short nor too
> long, so it was pretty much manageable, so yes, that was useful. Thanks!
Thanks for your prompt action.
I only reviewed the patches to make sure they are indeed trivial. That
is, mechanical version bump, or upstream backports.
> What would be even more useful (and this is valid for everyone) is to
> review complex patches too, because those are the ones that take more
> time (version bumps are indeed trivial and seldom get a second thought
> from my part).
I am fully aware of the review bandwidth shortage that makes complex
patches linger in patchwork queue. The thing is that the queue length
seems to hide trivial patches that are closer to the distant end of the
queue. So I took action in hope to bring some of these patches back to
front, at least on the mailing list. I am glad it worked.
The immediate trigger for me was the libcurl bump (commit 1e735c48372)
that was also a security update that went through some trouble with
distros[1]. Was Buildroot affected as well? Anyway, the update delay
made libcurl bump miss the last 2022.02.x release, which is unfortunate.
[1] https://daniel.haxx.se/blog/2023/03/29/pre-notification-dilemmas/
> Anyway, thanks for the effort, and if you send another list, this length
> and content is nice. 👍
Thanks,
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-05-07 5:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 5:17 [Buildroot] List of trivial old patches Baruch Siach via buildroot
2023-05-05 11:58 ` Nicolas Cavallari
2023-05-05 13:24 ` Arnout Vandecappelle via buildroot
2023-05-06 15:16 ` Yann E. MORIN
2023-05-07 4:17 ` Baruch Siach via buildroot [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=877ctkaf3h.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=yann.morin.1998@free.fr \
/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