Adding upstream version 0.1.32.upstream/0.1.32

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 12 insertions, 1 deletions

diff --git a/debputy.pod b/debputy.pod
index c53fa23..3687398 100644
--- a/debputy.pod
+++ b/debputy.pod
@@ -171,7 +171,7 @@ providing the results.
 If you rely on the exit code, you are recommended to explicitly pass the relevant variant of the
 flag even if the current default matches your wishes.
 
-=item B<--missing-style-is-ok>
+=item B<--unknown-or-unsupported-style-is-ok>, B<--missing-style-is-ok>
 
 By default, B<debputy reformat> will exit with an error when it cannot determine which style to
 use. This is generally what you want for "per package" CI or other lint checks to inform you that
@@ -186,6 +186,17 @@ It can also be useful for scripts or automated mass-edits where you want B<debpu
 the changes you did if there is a known style without being hampered by the packages that
 have no known style.
 
+The B<--missing-style-is-ok> is a deprecated name since it does not correctly imply that
+unsupported styles are also considered ok.
+
+=item B<--supported-style-is-required>
+
+Exit with an error if no supported style can be found. This is the default behaviour but
+this option can be used to override settings to disable it. The error does not distinguish
+between no style found or an unsupported style found (both lead to an error).
+
+If you rely on the exit code, please set this option explicitly.
+
 =back
 
 =item lint