Neither of these problems existed in the patches Gerd and I posted, so
presumably they came about by trying to merge the two patch sets?
It means I squashed the resolutions incorrectly. I could add a
bisectability test but that would take a long time to run...
Indeed.
How can we avoid this happening in future? What process could we have
used to avoid it?
There are a few ways. This was all sitting in staging for quite some
time so poking at staging proactively could have helped.
I stopped looking at staging. You stuff almost everything you find on
the list into staging, so seeing patches queued up there doesn't
indicate anything ...
cheers,
Gerd
