Hi, On 3 October 2014 12:31, Pekka Paalanen <[email protected]> wrote:
> On Fri, 3 Oct 2014 13:00:05 +0300 > Giulio Camuffo <[email protected]> wrote: > > 2014-10-01 11:45 GMT+03:00 Pekka Paalanen <[email protected]>: > > > How about we started using http://patchwork.freedesktop.org/ ? > > > > > > Apparently it works fine for Mesa et al., right? > > > > > > I believe it picks up patch emails from the mailing lists automatically > > > and creates issues, and with a git hook at fd.o repos, a git-push can > > > automatically close issues. > > > > > > There was also some command line tool for the patchwork database, IIRC. > > > > > > It wouldn't change how we work: patches are good in the mailing list, > > > inline, we would still do review on the mailing list, etc. We would > > > just have an automatically maintained list of open patches. > > > > > > For the record, this was the announcement for Mesa: > > > > http://lists.freedesktop.org/archives/mesa-dev/2013-November/049293.html > > > > > > Wayland-devel mailing list gets patches to three different projects: > > > Wayland, Weston, and libinput. Is this a problem? Sometimes it is hard > > > for even humans to see which repository a patch is targeting. > > > > > > From a quick chat with tfheen, it seems like patchwork assumes 1:1 > > > between mailing lists and projects. OTOH, it looks like Xorg project in > > > patchwork gets patches to a myriad of different git repos, and you can > > > filter search results based on subject. > > > > > > People do already usually use something like "[PATCH weston v7]" to > > > identify the target, so filtering by subject should mostly work. > > > > How does this work if someone forgets the "weston" though? I know it > > happened to me at least one time. > > You would still see it in patchwork's unfiltered list, i.e. the default > view. It's totally possible to split and filter repos by hacking parsemail.py (so, doable, just annoying to preserve); on the other hand, I don't see that it's possible to move patches between projects, at least not without manual bashing inside the Django admin interface. So while I could implement a Wayland/Weston split, I've opted not to since misplaced patches would get dumped in the wrong side of things too often. But if it becomes a problem later on, we can split them easily enough. Ditto libinput/xkbcommon. Cheers, Daniel
_______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
