From 2d86ed946adba4460af258604205df93a7363d64 Mon Sep 17 00:00:00 2001 From: Antonio SJ Musumeci Date: Wed, 26 Mar 2025 14:32:04 -0500 Subject: [PATCH] Update docs on default create policy --- mkdocs/docs/faq/configuration_and_policies.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/mkdocs/docs/faq/configuration_and_policies.md b/mkdocs/docs/faq/configuration_and_policies.md index ec8e6481..0dad7868 100644 --- a/mkdocs/docs/faq/configuration_and_policies.md +++ b/mkdocs/docs/faq/configuration_and_policies.md @@ -19,6 +19,14 @@ filesystems and can be added or removed without any impact it is extremely easy to test and experiment with different settings. +## Why is epmfs the default create policy? + +Because it is a strict policy and therefore does not increase entropy +of the filesystem layout. If you don't explicitly choose a policy then +the layout stays the same. It is far easier to stop being strict than +fix the layout after having a loose policy. + + ## How can I ensure files are collocated on the same branch? Many people like the idea of ensuring related files, such as all the