Hi,

Tom has indicated that he would like Patman to move out of his tree. I
suggested on another thread[1] that I maintain it in my 'sjg' tree, so
here is a new thread to discuss this.

I have already done this for the qemu/efi/coreboot scripts as Tom has
NAK'ed patches for those.

For the other tools there is going to be quite a bit of churn, as I
would like to resolve most of the many Python warnings.

Given the shared source between the tools, it would be easier for me
to do the same for buildman, binman and qconfig. I am thinking that I
might try a move to allow Gitlab pull-requests for reviews on these as
well as the mailing list, if that is useful.

For tools which need to sync back to Tom's tree (i.e. not patman), I
or Tom could do a pull request every now and then, omitting any
changes that relate to pylint.

Please let me know your thoughts. The timing is good as I am going to
be sending out a new Patman feature in the next few weeks and it is a
few thousand more lines of code.

Regards,
Simon

[1] 
https://lore.kernel.org/u-boot/caflsztg7-ym0l8uujyn7jpsb1lbvoyo76cuwj+h719mfc97...@mail.gmail.com/

Reply via email to