From: Daniel Axtens <dja@axtens.net>
To: u-boot@lists.denx.de
Subject: [RFC PATCH 01/16] patman: Use test_util to show test results
Date: Tue, 07 Jul 2020 11:09:34 +1000 [thread overview]
Message-ID: <87d0583zch.fsf@dja-thinkpad.axtens.net> (raw)
In-Reply-To: <CAPnjgZ2f-AotZJnGaGKSXsR+Sp6AO_tkToa8pcD78CdD+p1MFw@mail.gmail.com>
Simon Glass <sjg@chromium.org> writes:
> Hi Daniel,
>
> On Sun, 5 Jul 2020 at 22:50, Daniel Axtens <dja@axtens.net> wrote:
>>
>> Daniel Axtens <dja@axtens.net> writes:
>>
>> > Hi Simon,
>> >
>> > I can't see a cover letter so apologies if I've misunderstood something
>> > basic, but this doesn't appear to apply to the patchwork tree - I'm
>> > guessing the patchwork relevance is with regards to the last few patches
>> > that (AFAICT) parse the patchwork web interface for information?
>>
>> Ah, nevermind, the cover letter got caught in moderation. I've released it.
>>
>> pwclient speaks the old, less documented XML-RPC API. We have a new
>> REST API which is much better documented, and is explorable
>> (e.g. https://patchwork.ozlabs.org/api/ and
>> https://patchwork.readthedocs.io/en/latest/api/rest/ )
>>
>> > I haven't fully digested the patches (and I lack a lot of context) but
>> > is there a reason the patchwork API isn't able to meet your needs here?
>> > (And if so, could we extend it rather than having you parse the frontend?)
>>
>> So these questions still stand but for the REST API.
>
> So use the REST API instead of the web page? That sounds fine to me.
> Is it generally enabled on patchwork servers?
I mean patman is your code so it's ultimately not my call :P But yes,
I'd strongly prefer you used the REST API! It is enabled on ozlabs.org
and kernel.org and has been for a while (~a couple of years).
> What is the status of pwclient? Is it dead? Is there a replacement?
> I'd love to use a Python library if one exists.
Stephen F is the expert on the client stuff, so I'm not going to make a
call on the status of pwclient. All I am confident to say is that I have
migrated to using 'git-pw' and I recommend others do so to too.
I'm not sure if a dedicated Python client library exists: the last time
I wanted to write a Python client app I found it simple enough to just
use the JSON that the API provides directly. But the place I'd start
with is git-pw.
Regards,
Daniel
> Regards,
> SImon
next prev parent reply other threads:[~2020-07-07 1:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 3:41 [RFC PATCH 00/16] RFC: patman: Collect review tags and comments from Patchwork Simon Glass
2020-07-06 3:41 ` [RFC PATCH 01/16] patman: Use test_util to show test results Simon Glass
2020-07-06 4:46 ` Daniel Axtens
2020-07-06 4:50 ` Daniel Axtens
2020-07-06 14:52 ` Simon Glass
2020-07-07 1:09 ` Daniel Axtens [this message]
2020-07-08 17:42 ` Stephen Finucane
2020-07-19 20:49 ` Simon Glass
2020-07-06 3:41 ` [RFC PATCH 02/16] patman: Move main code out to a control module Simon Glass
2020-07-19 20:49 ` Simon Glass
2020-07-06 3:41 ` [RFC PATCH 03/16] patman: Add a test that uses gitpython Simon Glass
2020-07-19 20:49 ` Simon Glass
2020-07-06 3:41 ` [RFC PATCH 04/16] patman: Allow creating patches for another branch Simon Glass
2020-07-19 20:49 ` Simon Glass
2020-07-06 3:41 ` [RFC PATCH 05/16] patman: Allow skipping patches at the end Simon Glass
2020-07-19 20:49 ` Simon Glass
2020-07-06 3:41 ` [RFC PATCH 06/16] patman: Convert to ArgumentParser Simon Glass
2020-07-19 20:49 ` Simon Glass
2020-07-06 3:41 ` [RFC PATCH 07/16] patman: Allow different commands Simon Glass
2020-07-19 20:49 ` Simon Glass
2020-07-06 3:41 ` [RFC PATCH 08/16] patman: Add a 'test' subcommand Simon Glass
2020-07-19 20:49 ` Simon Glass
2020-07-06 3:41 ` [RFC PATCH 09/16] patman: Allow disabling 'bright' mode with Print output Simon Glass
2020-07-19 20:49 ` Simon Glass
2020-07-06 3:41 ` [RFC PATCH 10/16] patman: Support collecting response tags in Patchstream Simon Glass
2020-07-19 20:49 ` Simon Glass
2020-07-06 3:41 ` [RFC PATCH 11/16] patman: Allow linking a series with patchwork Simon Glass
2020-07-06 3:41 ` [RFC PATCH 12/16] patman: Add a -D option to enable debugging Simon Glass
2020-07-06 3:42 ` [RFC PATCH 13/16] patchstream: Support parsing of review snippets Simon Glass
2020-07-06 3:42 ` [RFC PATCH 14/16] patman: Support checking for review tags in patchwork Simon Glass
2020-07-06 3:42 ` [RFC PATCH 15/16] patman: Support updating a branch with review tags Simon Glass
2020-07-06 3:42 ` [RFC PATCH 16/16] patman: Support listing comments from patchwork Simon Glass
2020-07-15 9:10 ` [RFC PATCH 00/16] RFC: patman: Collect review tags and comments from Patchwork Michal Simek
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=87d0583zch.fsf@dja-thinkpad.axtens.net \
--to=dja@axtens.net \
--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