From a04379e8fb5db7290e325b04c4e84aa8ba669558 Mon Sep 17 00:00:00 2001 From: Sean Whitton Date: Sat, 22 Jun 2019 18:35:09 +0100 Subject: dgit(1): expand on description of behaviour of --include-dirty See #930922. Signed-off-by: Sean Whitton --- dgit.1 | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'dgit.1') diff --git a/dgit.1 b/dgit.1 index bff3c51..f427c2b 100644 --- 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. -- cgit v1.2.3