When you call eg. "lscp" without specifiing device it does look in /proc/mounts for first nilfs device and use this. But i think it should not just take first device. It should check wheter the current working directory is inside a NILFS mount and use according device. Also it should work if i specify directory instead of device. eg. lscp /mnt/nilfs.
BTW there is nilfs2 plugin for thunar that can show checkpoints related to individual files and directories.
https://github.com/kazuki/thunar-nilfs2-plugin/
So you can basicaly list checkpoints that affect file or directory. This effectively means that you can list changes/versions of indivudal files and directories. It can be done trough GUI using mentioned plugin, but it cannot be done from commandline using nilfs-utils. That is kinda shame. I think this would be very usefull, because you don't have to go throught all checkpoints if you are just interested in history of particular file or subtree.
When you call eg. "lscp" without specifiing device it does look in /proc/mounts for first nilfs device and use this. But i think it should not just take first device. It should check wheter the current working directory is inside a NILFS mount and use according device. Also it should work if i specify directory instead of device. eg.
lscp /mnt/nilfs.BTW there is nilfs2 plugin for thunar that can show checkpoints related to individual files and directories.
https://github.com/kazuki/thunar-nilfs2-plugin/
So you can basicaly list checkpoints that affect file or directory. This effectively means that you can list changes/versions of indivudal files and directories. It can be done trough GUI using mentioned plugin, but it cannot be done from commandline using nilfs-utils. That is kinda shame. I think this would be very usefull, because you don't have to go throught all checkpoints if you are just interested in history of particular file or subtree.