On Sun, 2015-03-29 at 13:43 +0200, Kai Krakow wrote: > Concluding that: duperemove should probably not try to become smart about > filesystem boundaries. It should either cross them or not as it is now - the > option is left to the user (as is the task to supply proper cmdline > arguments with that). Couldn't it per default simply cross boundaries just within the same btrfs fs (i.e. amongst all it's subvolumes), since this seems to be the natural choice users want in most cases,... and via --no-xdev option or something like that it would be allowed to pass boundaries? Cheers, Chris.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
