dgit-maint-gbp(7): Mention --overwrite

[dgit.git] / dgit.1

diff --git a/dgit.1 b/dgit.1
index 81786315c4366c30f6550f07902369d65f2b3ba3..af23a5f31ab96f1176284dd6e9165ab9166db7d9 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -740,6 +740,16 @@ Your build or push will probably fail later.
 .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
@@ -989,6 +999,7 @@ non-dry-run dgit fetch first will help.
 .SH SEE ALSO
 \fBdgit\fP(7),
 \fBdgit-maint-merge\fP(7),
+\fBdgit-maint-gbp\fP(7),
 \fBcurl\fP(1),
 \fBdput\fP(1),
 \fBdebsign\fP(1),