[wraithm112]

I said "intentional hard-fork" for a reason. For everybody's reference, the bdb to leveldb hard-fork happened in early 2013. Everybody acted swiftly to correct the issue by downgrading to 0.7 if I recall correctly.

An accidental hard-fork is a completely different animal from an intentional contentious hard-fork where half of the network goes one way and the other half the other way for the foreseeable future.

[mike_hearn]

So did I. Please re-read my post. The same change that triggered the accidental fork was done smoothly later on, but the change was the same - it was a deliberate hard fork. You probably didn't notice because there was plenty of lead time and I don't think any miners got split off the chain, even though they could have.