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

diff --git a/dgit.1 b/dgit.1
index f7cbfbfb..cc10695a 100644
--- a/dgit.1
+++ b/dgit.1
@@ -736,6 +736,20 @@ 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.
+.TP
+.B --force-unsupported-source-format
+Carry on despite dgit not understanding your source package format.
+dgit will probably mishandle it.
+.TP
+.B --force-dsc-changes-mismatch
+Do not check whether .dsc and .changes match.
+The archive will probably reject your upload.
+.TP
+.BR --force-import-gitapply-absurd " | " --force-import-gitapply-no-absurd
+Force on or off the use of the absurd git-apply emulation
+when running gbp pq import
+when importing a package from a .dsc.
+See Debian bug #841867.
 .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