That's sorta how CouchDB does it's default conflict resolution. In a conflict, by default CouchDB picks the revision with the longest edit chain. Couch doesn't

That's sorta how CouchDB does it's default conflict resolution. In a conflict, by default CouchDB picks the revision with the longest edit chain. Couch doesn't throw out the other conflicts, it hangs on to them so applications can make their own decisions about resolution.