From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 0/9] Remove packages
Date: Tue, 6 Jan 2026 21:24:18 +0100 [thread overview]
Message-ID: <20260106212418.1f980d25@windsurf> (raw)
In-Reply-To: <20260106200115.1985522-1-bernd@kuhls.net>
Hello Bernd,
On Tue, 6 Jan 2026 21:01:05 +0100
Bernd Kuhls <bernd@kuhls.net> wrote:
> Thomas Petazzoni (5):
> package/libsvg-cairo: remove package
> package/libsvg: remove package
> package/gconf: remove package, broken
> package/criu: remove package
> package/cvs: drop package
I'm curious to understand why you integrated those into your series? Of
course, there's no harm, but I'm not sure to see the benefit. Did you
make some changes/improvements?
Indeed, the downside is that this supersedes patches that are not from
you, so you can't mark the previous ones as superseded in patchwork,
requiring more patchwork "maintenance" from our side, with no clear
benefit?
Of course, when you adopt a patch from someone else because you make
improvements, on build on top of it in your series, it totally makes
sense to take the patch from someone else. But here, I'm not sure to
see the point?
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-01-06 20:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 20:01 [Buildroot] [PATCH v2 0/9] Remove packages Bernd Kuhls
2026-01-06 20:01 ` [Buildroot] [PATCH v2 1/9] package/libsvg-cairo: remove package Bernd Kuhls
2026-01-16 20:59 ` Thomas Petazzoni via buildroot
2026-01-28 17:24 ` Arnout Vandecappelle via buildroot
2026-01-06 20:01 ` [Buildroot] [PATCH v2 2/9] package/libsvg: " Bernd Kuhls
2026-01-28 17:24 ` Arnout Vandecappelle via buildroot
2026-01-06 20:01 ` [Buildroot] [PATCH v2 3/9] package/gconf: remove package, broken Bernd Kuhls
2026-01-28 17:24 ` Arnout Vandecappelle via buildroot
2026-01-06 20:01 ` [Buildroot] [PATCH v2 4/9] package/criu: remove package Bernd Kuhls
2026-01-16 21:00 ` Thomas Petazzoni via buildroot
2026-01-28 17:24 ` Arnout Vandecappelle via buildroot
2026-01-06 20:01 ` [Buildroot] [PATCH v2 5/9] package/cvs: drop package Bernd Kuhls
2026-01-28 17:24 ` Arnout Vandecappelle via buildroot
2026-01-06 20:01 ` [Buildroot] [PATCH v2 6/9] package/dbus-triggerd: remove package Bernd Kuhls
2026-01-28 17:24 ` Arnout Vandecappelle via buildroot
2026-01-06 20:01 ` [Buildroot] [PATCH v2 7/9] package/libcec: remove optional dependency to lockdev Bernd Kuhls
2026-01-06 20:01 ` [Buildroot] [PATCH v2 8/9] package/libgphoto2: " Bernd Kuhls
2026-01-28 17:24 ` Arnout Vandecappelle via buildroot
2026-01-06 20:01 ` [Buildroot] [PATCH v2 9/9] package/lockdev: remove package Bernd Kuhls
2026-01-16 21:00 ` Thomas Petazzoni via buildroot
2026-01-28 17:24 ` Arnout Vandecappelle via buildroot
2026-01-06 20:24 ` Thomas Petazzoni 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=20260106212418.1f980d25@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=thomas.petazzoni@bootlin.com \
/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