X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=dgit.1;h=f7cbfbfb8f673f67b7daa4bf9b9142f0b40e6a4b;hp=d6ac8b25a907be3b9e857352613114e1862291ec;hb=37913654d58e03354aa4d5a6aa5afb9c5aeca6b7;hpb=d206873437a8ee676eeb2806754a57fa938c9a4c

diff --git a/dgit.1 b/dgit.1
index d6ac8b25..f7cbfbfb 100644
--- a/dgit.1
+++ b/dgit.1
@@ -721,6 +721,21 @@ instead.  Furthermore, the specified directory will be emptied,
 removed and recreated before dgit starts, rather than removed
 after dgit finishes.  The directory specified must be an absolute
 pathname.
+.TP
+.BI --force- something
+Instructs dgit to try to proceed despite detecting
+what it thinks is going to be a fatal problem.
+.B This is probably not going to work.
+These options are provided as an escape hatch,
+in case dgit is confused.
+(They might also be useful for testing error cases.)
+.TP
+.B --force-unrepresentable
+Carry on even if
+dgit thinks that your git tree contains changes
+(relative to your .orig tarballs)
+which dpkg-source is not able to represent.
+Your build or push will probably fail later.
 .SH WORKFLOW - SIMPLE
 It is always possible with dgit to clone or fetch a package, make
 changes in git (using git-commit) on the suite branch