Bisect on patchset boundaries ?

The "buggy intermediate versions" problem is one that I would have expected more attention to be drawn to. I've done a few bisects and had my filesystem fail to mount on several cuts during one run.

A bisect that throws you into the middle of a patch set that messes with your filesystem is a dangerous place to be; especially when you ask 'normal' users to run a bisect on their everyday machines without warning them that they are potentially about to expose their data to random collections of code.

The problem is that all patches are supposed to be non-toxic - and git is deliberately not good at revisionist history ;)

That means that marking 'safe' bisect points is hard - but maybe a step in the right direction would be worth cutting on patchset boundaries?

Or maybe an external (well, inside .git/) list of 'good' commits eg rc releases?

Obviously this would make the bisect slightly less efficient but it may reduce the risk.