summaryrefslogtreecommitdiff
path: root/dgit.1
diff options
context:
space:
mode:
Diffstat (limited to 'dgit.1')
-rw-r--r--dgit.115
1 files changed, 10 insertions, 5 deletions
diff --git a/dgit.1 b/dgit.1
index 7bd8b05..ed193b0 100644
--- a/dgit.1
+++ b/dgit.1
@@ -643,11 +643,16 @@ fails even on ignored untracked files.
This could perhaps be used to detect bugs in your rules clean target.
.TP
.BR -N " | " --new
-The package is or may be new in this suite. Without this, dgit will
+The package is, or may be, new in this suite. Without this, dgit will
refuse to push.
-It may (for Debian, will) be unable to access the git
-history for any packages which have been newly pushed and have not yet
-been published.
+Needing --new is not unusual; for example,
+it is frequently needed for uploading to Debian experimental.
+
+Note that dgit may be unable to access the git
+history for an entirely new package which has not been accepted by
+the archive.
+So for an entirely new package you need to properly coordinate
+with anyone else who might upload.
.TP
.BR --include-dirty
Do not complain if the working tree does not match your git HEAD,
@@ -1320,7 +1325,7 @@ the required checks and leaves the new .dsc in a temporary file,
but does not sign, tag, push or upload.
This is not a very good simulation.
-It can easily go wrong for ways that a for-real push wouldn't.
+It can easily go wrong in ways that a for-real push wouldn't.
.TP
.BR \-\-damp-run " | " \-L
Go through many more of the motions: do everything that doesn't