Hi all, there's two main themes here, intertwined because it's hard to properly separate the two:
* Start encouraging separate dim tag-branch and dim pull-request. It's not a requirement (yet) but start supporting it better. First, make tag-branch show changes since last tag or upstream. Second, make pull-request take all of the previous tags into account. The future development here would be to *not* unconditionally tag in pull-request. * Start migrating away from the split drm-intel-next-queued and drm-intel-next model. Remove the drm-intel-testing step. First we move towards using drm-intel-next-queued exclusively. The future development here would be to add drm-intel-next to nightly.conf followed by a potential flag day switch from drm-intel-next-queued to drm-intel-next. All of the patches here should be incremental. No need to apply all at once. That might be a good option, since dim is pretty hard to test, so I've mostly tested bits and pieces out of context. BR, Jani. Jani Nikula (7): dim: abstract driver date update to a subcommand dim: stop generating drm-intel-testing requests dim: return early on tag-branch fail dim: abstract helper for listing unmerged tags dim: optionally launch gitk with changelog on dim tag-branch dim: include all unmerged tags in the pull request mail dim: replace drm-intel-next usage with drm-intel-next-queued dim | 169 ++++++++++++++++++++++++++++------------------------------------ dim.rst | 33 +++++-------- 2 files changed, 86 insertions(+), 116 deletions(-) -- 2.11.0 _______________________________________________ dim-tools mailing list dim-tools@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dim-tools