Bo Yang <struggleyb.nku@xxxxxxxxx> writes: > Both single range clone and deeply clone are supported. Please explain what you mean by "deeply clone" (no, not just a language nitpick that it should at least be "deep clone"), and document which one needs to be used in what situations to help people who would want to decide which of these functions to call. What I am trying to get at is that you might want to have only one kind of clone that is _semantically_ deep (i.e. the list is copied, but the elements are shared with refcounting), but makes a copy of the element that is being updated on demand (i.e. have an API function to allow users to modify, which internally does copy-on-write if it is still shared). I don't know that kind of arrangement makes sense; it depends on how the cloned ranges are used but I haven't looked at the callers. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html