debian/rules: Break out specpkg_install_common

[dgit.git] / dgit.1

diff --git a/dgit.1 b/dgit.1
index f427c2b778fa503d99fedbd3ad11ee26b8093095..6e0c4f1186c2113795bc24cb14db02f396beef78 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -647,8 +647,11 @@ Note that this does
 .BR not
 prevent dgit from cleaning your tree, so if the changes in your
 working tree are in the form of untracked files, those might still be
-deleted.  If you want to include untracked files in the build, you can
-use --clean=none in addition to --include-dirty.  Note that this
+deleted, especially with --clean=git.
+If you want to include untracked files in the build, you can
+use --clean=none or --clean=dpkg-source[-d]
+in addition to --include-dirty.
+Note that this
 combination can fail if the untracked files are under
 \fIdebian/patches/\fR.
 .TP
@@ -862,7 +865,7 @@ Do not check whether source format `3.0 (quilt)' metadata needs
 fixing up.  If you use this option and the metadata did in fact need
 fixing up, dgit push will fail.
 .TP
-.BR -- [ quilt= ] gbp " | " -- [ quilt= ] dpm " | " --quilt=unapplied " | " -- [ quilt= ] baredebian [ +tarball ]
+.BR -- [ quilt= ] gbp " | " -- [ quilt= ] dpm " | " --quilt=unapplied " | " -- [ quilt= ] baredebian [ +git | +tarball ]
 Tell dgit that you are using a nearly-dgit-compatible git branch,
 aka a
 .BR "maintainer view" ,
@@ -895,6 +898,8 @@ that any changes to upstream .gitignore files are represented as
 patches in debian/patches).
 
 .B --quilt=baredebian
+(or its alias
+.BR --quilt=baredebian+git )
 specifies that your HEAD contains only a debian/ directory,
 with any changes to upstream files represented as
 patches in debian/patches.