Hi Patrick,
When going through the list of submittable patches i ran into a two
problems and also got a question:
When a patch before other patches gets abandoned, those patches can no
longer be submitted. Example: CB:66324
When submitting the first patch of a patch series, somehow the following
patches now have merge conflicts even though they shouldn't have any
merge conflict. Example: I submitted CB:66272 and now CB:66273 and
following have merge conflicts which they didn't have before. I
definitely want to submit a patch train patch by patch and not just the
last submittable patches including all patches before to make sure that
I looked at each individual patch when submitting.
When part of a patch train gets re-pushed due to some small fixes that
won't affect patches after a certain patch and then all patches from the
patch series are reviewed and submittable, how will the case that later
patches are on top of outdated patches be handled? Previously the latest
version of each individual patch was used which is the correct behavior,
but I'm not sure if this is still the case with the new approach.
Especially the second problem is a dealbreaker for me. Not sure if this
can be fixed by some configuration change; if not, I'd like to go back
to the previously used cherry-pick submit method.
Regards,
Felix
_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
