Skip to content
Snippets Groups Projects
  1. Jan 29, 2022
  2. Jan 27, 2022
    • Javier Martinez Canillas's avatar
      dim: Check that patches have git-format-patch default prefixes · 132510ea
      Javier Martinez Canillas authored and Simona Vetter's avatar Simona Vetter committed
      
      By default the git-format-patch command generates patches with prefixes
      for the source and destination (-p1), and is also what git-am uses as a
      default. The command strips the first leading path component when patch
      is applied (unless a different -p<num> argument is used).
      
      But the patch generating behaviour can be changed with git-format-patch
      --no-prefix argument (or setting 'diff.noprefix = true' in .gitconfig).
      
      Patches with no source and destination prefixes can confuse the git-am
      3-way merge logic, since stripping the first path component will lead
      to wrong paths for newly added files.
      
      To avoid this, check that patches to apply are using git-format-patch's
      defaults prefixes to make sure that git-am defaults are safe to use too.
      
      Since there are developers that generate patches without using git, make
      this an error but allow to still continue when using the dim -f option.
      
      Signed-off-by: default avatarJavier Martinez Canillas <javierm@redhat.com>
      Signed-off-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      132510ea
    • Simona Vetter's avatar
      dim: Update drm-misc maintainer list · 0666fb79
      Simona Vetter authored
      
      Way out of date.
      
      Reviewed-by: default avatarMaarten Lankhorst <maarten.lankhorst@linux.intel.com>
      Cc: Jani Nikula <jani.nikula@linux.intel.com>
      Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
      Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
      Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
      Cc: Lyude Paul <lyude@redhat.com>
      Cc: Thomas Zimmermann <tzimmermann@suse.de>
      Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
      Cc: Maxime Ripard <mripard@kernel.org>
      Signed-off-by: default avatarDaniel Vetter <daniel.vetter@intel.com>
      0666fb79
    • Simona Vetter's avatar
      dim: Caution more against topic branches · 74c11c32
      Simona Vetter authored
      
      They're very often just beaurocratic paperwork pushing because
      maintainers refuse to give acks for merging patches through a single
      tree. I guess the snarky intro wasn't clear enough, so elaborate.
      
      Given that we don't even talk about topic branches anywhere else in
      the docs hopefully this makes things a bit clearer.
      
      v2: Fix typo (Maarten)
      
      Reviewed-by: default avatarMaarten Lankhorst <maarten.lankhorst@linux.intel.com>
      Cc: Jani Nikula <jani.nikula@linux.intel.com>
      Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
      Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
      Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
      Cc: Lyude Paul <lyude@redhat.com>
      Cc: Thomas Zimmermann <tzimmermann@suse.de>
      Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
      Cc: Maxime Ripard <mripard@kernel.org>
      Signed-off-by: default avatarDaniel Vetter <daniel.vetter@intel.com>
      74c11c32
  3. Jan 14, 2022
  4. Nov 24, 2021
  5. Nov 11, 2021
  6. Oct 27, 2021
  7. Aug 17, 2021
  8. Aug 16, 2021
  9. Jul 13, 2021
  10. Apr 29, 2021
  11. Dec 18, 2020
  12. Dec 17, 2020
  13. Dec 15, 2020
    • Simon Ser's avatar
      dim: fix handling of 8-bit non-UTF-8 messages · d79c5784
      Simon Ser authored and Simona Vetter's avatar Simona Vetter committed
      
      Python's open() function will return a file object that decodes input
      bytes to an UTF-8 string. Python assumes all files are UTF-8 by default
      (unless an explicit encoding param is passed).
      
      This works fine with 7-bit and UTF-8 messages. However, when a message
      uses a 8-bit Content-Transfer-Encoding and a non-UTF-8 charset (such as
      iso-8859-1), Python will error out.
      
      To prevent this, open the file in binary mode to prevent Python from
      doing any charset conversion under-the-hood.
      
      Signed-off-by: Simon Ser's avatarSimon Ser <contact@emersion.fr>
      Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
      Signed-off-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      d79c5784
  14. Dec 06, 2020
  15. Nov 25, 2020
  16. Nov 24, 2020
  17. Nov 20, 2020
  18. Nov 10, 2020
    • Jani Nikula's avatar
      dim: change the drm-intel-next and drm-intel-next-queued process · c7b6928a
      Jani Nikula authored
      
      Remove the special casing of drm-intel-next/drm-intel-next-queued
      tagging and pull requests. Instead of having a two-step process for
      dinq, follow the same pull request process for all branches. As the
      first step, use drm-intel-next-queued for pull requests, and ignore
      drm-intel-next for now. The change is only relevant for maintainers.
      
      In the future, we'll want to switch from drm-intel-next-queued to
      drm-intel-next completely. This will need a flag day switch for all
      committers and maintainers.
      
      We also decouple driver date update from dinq pull requests. We may want
      to apply the driver date update to drm-intel-gt-next branch instead.
      
      With the change, we also lose the ability to add multiple drm-intel-next
      tags, and create a single pull request for them. In practice, we haven't
      really used this possibility, as it lacks the merging of the annotated
      tag changelogs together, missing information. We may want to resurrect
      the feature in an improved form in the future, generalized for all
      branches.
      
      Cc: Daniel Vetter <daniel@ffwll.ch>
      Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
      Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
      Acked-by: default avatarRodrigo Vivi <rodrigo.vivi@intel.com>
      Signed-off-by: default avatarJani Nikula <jani.nikula@intel.com>
      c7b6928a
  19. Oct 26, 2020
  20. Sep 11, 2020
  21. Sep 10, 2020
  22. May 14, 2020
  23. Mar 31, 2020
  24. Dec 20, 2019
  25. Dec 19, 2019
  26. Dec 17, 2019
  27. Nov 15, 2019
  28. Nov 14, 2019
  29. Sep 03, 2019
Loading