On Tue, Apr 29, 2025 at 08:35:24AM -0600, Simon Glass wrote:
> Hi Tom,
> 
> On Tue, 29 Apr 2025 at 07:48, Tom Rini <tr...@konsulko.com> wrote:
> >
> > On Tue, Apr 29, 2025 at 07:21:57AM -0600, Simon Glass wrote:
> >
> > > This series moves patman to use asyncio instead of ThreadPoolExecutor
> > > since it makes it easier to handle requests sent from different parts
> > > of the code.
> > >
> > > It also includes some updates to bring patman in line with the other
> > > major Python tools (buildman and binman).
> > >
> > > With this series, we have a better basis to add support for syncing more
> > > data from a patchwork server.
> > >
> > > After this, the next step it to add a new 'patman series' subcommand, to
> > > track and manage series workflow.
> >
> > This conflicts with master, please rebase this if you intend for it to
> > be merged to mainline.
> 
> I will take a look and see what patches my tree is missing.
> 
> >  And to avoid confusion, while I think managing
> > these python projects in this manner (and not AFAICT following python
> > best practices) makes life harder for everyone else, that is not me
> > NAK'ing taking more patches, I continue to be compromising and "Saying
> > Yes" to things you do that I disagree with on non-arbitrary technical
> > grounds.
> 
> I'm open to managing them in my tree if that helps. For now it seems
> like too much work to manage them separately, but if someone wants to
> volunteer to help, I could do it.

Again, if you won't manage them standalone as seems to be normal best
practice, we'll just keep them in mainline. It's up to you if they
diverge or not, but it would be easy to avoid I would think.

-- 
Tom

Attachment: signature.asc
Description: PGP signature

Reply via email to