From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Douglas Anderson <dianders@chromium.org>,
Sean Anderson <seanga2@gmail.com>
Subject: Re: [PATCH 0/5] patman: Separate gitutil fully
Date: Tue, 8 Apr 2025 16:13:24 -0600 [thread overview]
Message-ID: <20250408221324.GA5495@bill-the-cat> (raw)
In-Reply-To: <20250407105151.689453-1-sjg@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]
On Mon, Apr 07, 2025 at 10:51:42PM +1200, Simon Glass wrote:
>
> The gitutil module uses Patman's settings module, which is not allowed
> as it is supposed to be a separate package. This series ties up this
> dependency.
>
> This series depends on these two patches being applied:
>
> https://patchwork.ozlabs.org/project/uboot/patch/20250227192735.406389-1-sjg@chromium.org/
> https://patchwork.ozlabs.org/project/uboot/patch/20250328130225.2607974-1-sjg@chromium.org/
>
>
> Simon Glass (5):
> patman: Untangle settings from gitutil
> patman: Pass the alias dict into gitutil.build_email_list()
> patman: Pass the alias dict into gitutil.email_patches()
> patman: Pass aliases to Series.MakeCcFile()
> patman: Update Series.ShowActions() to pass alias
>
> tools/patman/control.py | 11 ++++++++---
> tools/patman/func_test.py | 8 ++++----
> tools/patman/series.py | 32 ++++++++++++++++++++++----------
> tools/u_boot_pylib/gitutil.py | 34 ++++++++++++++--------------------
> 4 files changed, 48 insertions(+), 37 deletions(-)
I just want to reiterate my question / request to host these outside of
the U-Boot sources themselves so they can be managed (both in the sense
of U-Boot as user and as maintainer of sources) following normal Python
best practices? I'd be fine even with something under
https://source.denx.de/u-boot/<something>/patman, etc.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-04-08 22:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 10:51 [PATCH 0/5] patman: Separate gitutil fully Simon Glass
2025-04-07 10:51 ` [PATCH 1/5] patman: Untangle settings from gitutil Simon Glass
2025-04-07 10:51 ` [PATCH 2/5] patman: Pass the alias dict into gitutil.build_email_list() Simon Glass
2025-04-07 10:51 ` [PATCH 3/5] patman: Pass the alias dict into gitutil.email_patches() Simon Glass
2025-04-07 10:51 ` [PATCH 4/5] patman: Pass aliases to Series.MakeCcFile() Simon Glass
2025-04-07 10:51 ` [PATCH 5/5] patman: Update Series.ShowActions() to pass alias Simon Glass
2025-04-08 22:13 ` Tom Rini [this message]
2025-04-09 13:04 ` [PATCH 0/5] patman: Separate gitutil fully Simon Glass
2025-04-09 13:08 ` Simon Glass
2025-04-09 15:18 ` Tom Rini
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=20250408221324.GA5495@bill-the-cat \
--to=trini@konsulko.com \
--cc=dianders@chromium.org \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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