On Mon, Nov 09, 2015 at 10:45:14AM +0200, Jani Nikula wrote: > On Sun, 08 Nov 2015, Damien Lespiau <damien.lespiau@xxxxxxxxx> wrote: > > There are two new patchwork projects then: > > > > http://patchwork.freedesktop.org/project/intel-gpu-tools/ > > http://patchwork.freedesktop.org/project/libdrm-intel/ > > > > I've also run the sorting on all the existing patches so the entries > > that were historically in the intel-gfx project are now in those new > > projects. > > Is it possible to manually move patches between projects? Damn, you noticed! No, it's not (yet?) possible. > > There is still some work left to limit the noise of those lists of > > patches, eg. some patches are still marked as New but, in reality, they > > have been merged. Solving that is quite important and high-ish the TODO > > list. > > This may be due to git am -3 subtly changing the patch, or the committer > not-so-subtly changing the patch [*], while applying, and the git hook > on fdo doesn't recognize the patch. Since we've started to add the Link: > tag to patches, we could use that extra bit of info in the hook to link > commits to patchwork. That would work for us, but not in the general case (for other projects). I was thinking of using some kind of other heuristic, eg. (subject, commit message, files touched) with a levenshtein distance on text to allow typo correction. Just for us, we could take a shortcut and make dim do something always correct based on the message-id, I'll have a think. -- Damien _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
