chiark / gitweb /
dgit(1): expand on description of behaviour of --include-dirty
authorSean Whitton <spwhitton@spwhitton.name>
Sat, 22 Jun 2019 17:35:09 +0000 (18:35 +0100)
committerIan Jackson <ijackson@chiark.greenend.org.uk>
Sun, 30 Jun 2019 20:11:18 +0000 (21:11 +0100)
See #930922.

Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
dgit.1

diff --git a/dgit.1 b/dgit.1
index bff3c51892ec69cf11098dc8131b7ab0a39fceb9..f427c2b778fa503d99fedbd3ad11ee26b8093095 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -642,6 +642,15 @@ include the changes from your working tree.
 This can be useful with build, if you plan to commit later.  (dgit
 push will still ensure that the .dsc you upload and the git tree
 you push are identical, so this option won't make broken pushes.)
+
+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
+combination can fail if the untracked files are under
+\fIdebian/patches/\fR.
 .TP
 .BR --ignore-dirty
 Deprecated alias for --include-dirty.