Hi Christopher, Christopher Baines <m...@cbaines.net> skribis:
> So, I was trying to work out how to update a series of patches, and > asked on the Patchwork mailing list [1], and discovered there's actually > another codebase with different features [2]. This Patchwork-FDO fork > does have a page that just displays series [3]. > > 1: https://lists.ozlabs.org/pipermail/patchwork/2018-November/005674.html > 2: https://gitlab.freedesktop.org/patchwork-fdo/patchwork-fdo/ > 3: > https://patchwork.freedesktop.org/project/intel-gfx/series/?ordering=-last_updated Interesting. > In terms of patch tracking, I'm thinking on Patchwork and Debbugs > independently, while I think it would be possible to integrate the two, > Patchwork has the tracking capabilities of Debbugs, so if Patchwork ever > becomes useful for automated testing of patches, it would probably > remove the need to use Debbugs to track patches (not actual bugs and > issues). Yes maybe, though Debbugs has features that make it attractive to me (SOAP interface and Emacs interface, properties attached to “bugs”, etc.) > Anyway, I think the next thing to try and do is get something > (Patchwork, Patchwork-FDO, Debbugs/issues.guix.info) triggering tests > for patches. I still need to compare the two Patchwork codebases to see > if they differ in this respect. Sounds like a plan! Thanks, Ludo’.
