You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently snapper create-config will always create a btrfs subvolume called ".snapshots" and will fail if there's already a file at the location /.snapshots. This makes it difficult to configure a custom subvolume to use for snapshots (see also #54).
How about adding a command line flag snapper create-config --no-subvolume which would disable the creation of the subvolume?
Currently
snapper create-config
will always create a btrfs subvolume called ".snapshots" and will fail if there's already a file at the location/.snapshots
. This makes it difficult to configure a custom subvolume to use for snapshots (see also #54).How about adding a command line flag
snapper create-config --no-subvolume
which would disable the creation of the subvolume?This would allow for a workflow like this:
The text was updated successfully, but these errors were encountered: