summaryrefslogtreecommitdiff
path: root/dgit.1
diff options
context:
space:
mode:
authorIan Jackson <ijackson@chiark.greenend.org.uk>2016-10-23 16:47:29 +0100
committerIan Jackson <ijackson@chiark.greenend.org.uk>2016-10-24 01:50:22 +0100
commit18e3479f8737622d5e3ff964652dade72f82c897 (patch)
treeffbc3e5d5842d33b5305dc60b048097df6701510 /dgit.1
parentd6e357b6f8dae996d00fea732910d24ca82cea26 (diff)
Provide --force-unsupported-source-format
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
Diffstat (limited to 'dgit.1')
-rw-r--r--dgit.14
1 files changed, 4 insertions, 0 deletions
diff --git a/dgit.1 b/dgit.1
index f7cbfbf..8178631 100644
--- a/dgit.1
+++ b/dgit.1
@@ -736,6 +736,10 @@ 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.
.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