On Thu, 2018-11-22 at 09:58 -0500, Konstantin Ryabitsev wrote: > Hi, all: > > I was looking into integrating git with some of the projects so that > applied patches can be auto-accepted and archived and I found out that > while the XMLRPC API knows how to look up a patch by its hash, the REST > API is not able to filter patches by hash. The main reason I wanted to > stick to the REST API is because it allows me to use an API token > instead of a username/password. > > So, two questions, really -- is the goal to retain both APIs, or is the > REST API supposed to eventually fully replace the other?
Yes, the XML-RPC API should go away in 3.0. > And if that is > the case, would it be possible to teach the REST API how to filter by > hash? Yeah, we should probably add this. I imagine we could expose this at the top-level API, along with numeric IDs and message-ID (coming soon). Just need someone to write that patch, I guess, as I don't know when I'll have time to do it myself. Stephen PS: Sorry for the massively delayed reply: Patchwork has taken a back seat to some other side projects of mine over the past few months. > Thanks, > -K > _______________________________________________ > Patchwork mailing list > Patchwork@lists.ozlabs.org > https://lists.ozlabs.org/listinfo/patchwork _______________________________________________ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
