On Sat, Oct 24, 2015 at 01:02:21PM +0100, P??draig Brady wrote: > I'm a bit worried about the sparse expansion and default reflinking > which might preclude cp(1) from using this call in most cases, but I will > test and try to use it. coreutils has heuristics for determining if files > are remote, which we might use to restrict to that use case. Can you explain why reflinking and hole expansion are an issue if done locally and not if done remotely? I'd really like to make the call as usable as possible for everyone, but we really need clear semåntics for that. Also note that Annas current series allows for hole filling - any decent implementation should not do them, but that's really a quality of implementation and not an interface issue. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
