Probably the largest and most annoying part of the MR process that @marlitas @matthew-blackman @samreid and I worked on this past week is when there are a few commits needed to "fix" a patch. The current process means making a new patch for each commit. I wonder if @jonathanolson and I could work on potentially having a different type of "patch application" for the MR process.
The main issue here would be "transactional" handling of cherry picks. Of 5 commits, what if only 4 of them apply. Should the process stall out and let you fix it, or revert those 4 and say "your on your own".
Probably the largest and most annoying part of the MR process that @marlitas @matthew-blackman @samreid and I worked on this past week is when there are a few commits needed to "fix" a patch. The current process means making a new patch for each commit. I wonder if @jonathanolson and I could work on potentially having a different type of "patch application" for the MR process.
The main issue here would be "transactional" handling of cherry picks. Of 5 commits, what if only 4 of them apply. Should the process stall out and let you fix it, or revert those 4 and say "your on your own".