Omar Sandoval 563affcd42 libbtrfsutil: use top=0 as default for SubvolumeIterator() ... Right now, we're defaulting to top=5 (i.e, all subvolumes). The documented default is top=0 (i.e, only beneath the given path). This is the expected behavior. Fix it and make the test cases cover it. Reported-by: Jonathan Lemon <bsd@fb.com> Signed-off-by: Omar Sandoval <osandov@fb.com> Signed-off-by: David Sterba <dsterba@suse.com>		2018-11-26 16:45:11 +01:00
..
tests	libbtrfsutil: use top=0 as default for SubvolumeIterator()	2018-11-26 16:45:11 +01:00
.gitignore	libbtrfsutil: add Python bindings	2018-02-24 01:37:17 +01:00
btrfsutilpy.h	libbtrfsutil: add btrfs_util_deleted_subvolumes()	2018-03-06 11:28:37 +01:00
error.c	libbtrfsutil: add Python bindings	2018-02-24 01:37:17 +01:00
filesystem.c	libbtrfsutil: add filesystem sync helpers	2018-02-24 01:37:17 +01:00
module.c	libbtrfsutil: add btrfs_util_deleted_subvolumes()	2018-03-06 11:28:37 +01:00
qgroup.c	libbtrfsutil: add btrfs_util_deleted_subvolumes()	2018-03-06 11:28:37 +01:00
setup.py	libbtrfsutil: add btrfs_util_is_subvolume() and btrfs_util_subvolume_id()	2018-03-06 11:28:36 +01:00
subvolume.c	libbtrfsutil: use top=0 as default for SubvolumeIterator()	2018-11-26 16:45:11 +01:00