Hi all,
I've added a feature to sort the patches sent to intel-gfx into 3
buckets: i915, intel-gpu-tools and libdrm. This sorting relies on
tagging patches, using the subject prefixes (which is what most people
do already anyway).
- i915 (intel-gfx): catchall project, all mails not matching any of
the other 2 projects will end up there
- intel-gpu-tools: mails need to be tagged with i-g-t, igt or
intel-gpu-tools
- libdrm-intel: mails need to be tagged with libdrm
This tagging can be set up per git repository with:
$ git config format.subjectprefix "PATCH i-g-t"
And use git send-email as usual. A note of caution though, using the
command line argument --subject-prefix will override the one configured,
so the tag will have to be repeated. To limit the number of things one
needs to think about I'd suggest to use --reroll-count to tag patches
with the v2/v3/... tags. I'm more and more thinking that wrapping the
sending logic for developers into the git-pw command would be a good
thing (especially for --in-reply-to) but that'd be for another time.
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.
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.
HTH,
--
Damien
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
