> I will encourage to do it before this patch gets into the codebase.
The duplicate peerinfo object issue is different from the problems in the current generation number scheme. I don't see why this patch needs to wait. We may need to keep volume-snapshot-clone.t disabled until the time the duplicate peerinfo issue is resolved, or understood better. Does that make sense? _______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
