(Not) Merging fixes into next
(Not) Merging fixes into next
Posted Jan 19, 2025 10:29 UTC (Sun) by geert (subscriber, #98403)In reply to: (Not) Merging fixes into next by sima
Parent article: The many names of commit 55039832f98c
Thanks a lot!
I had heard DRM committers have access to shared rerere-resolutions, but didn't know the details (and didn't find it appropriate to ask for DRM commit access just for that ;-) How do you make git consider that branch for resolutions? Is having it as a remote sufficiently, or do you need extra setup or magic? The drm-tip and dim documentation do not describe how it works (not using dim).
I didn't know about drm-tip.
Will give it a try for next renesas-drivers release.
> At a ks years ago I think I was discussing with Stephen whether there's any interesting in sharing these in a standardized format, but there was no interest apparently.
Not everybody is at the Kernel Summit. And even if they are, they might miss that session/information...
Posted Jan 20, 2025 9:00 UTC (Mon)
by sima (subscriber, #160698)
[Link]
Posted Jan 20, 2025 9:09 UTC (Mon)
by sima (subscriber, #160698)
[Link]
(Not) Merging fixes into next
(Not) Merging fixes into next