Re: [PATCH 0/5] patman: Separate gitutil fully

[Tom Rini <trini@konsulko.com>]

[-- Attachment #1: Type: text/plain, Size: 2373 bytes --]

On Wed, Apr 09, 2025 at 07:04:48AM -0600, Simon Glass wrote:
> Hi Tom,
> 
> On Tue, 8 Apr 2025 at 16:13, Tom Rini <trini@konsulko.com> wrote:
> >
> > 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.
> 
> Yes I am working towards that. This series cleans up something missed
> in the last series.
> 
> After this series there is really just 'patchstream' left, which is
> used by buildman and patman. I haven't quite come to terms with the
> idea of moving it to u_boot_pylib yet.
> 
> What are the best practices you are referring to?

Hosting python projects in their own repository, and versioning them
and managing them via pip/etc.

> As to location, I can keep it in my tree and just delete it from yours
> if you like.

That would be very silly. Aside from the whole thing about you needing
to close down your fork, which this isn't even about.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]