autopkgtests: provide t-git and pari-extra_3-1.git.tar (not currently used)

[dgit.git] / dgit.1

diff --git a/dgit.1 b/dgit.1
index 61c4aa3e42328faeeecc0b3f61a6339d6f60a553..7e74d5b77f62fdfc2ad5782c3973e8b9b4907c62 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -361,13 +361,14 @@ filename suggests it is for the right package and version - or,
 if there is a _multi.changes file, dgit uses that.
 .TP
 .BI --existing-package= package
-dgit push needs to canonicalise the suite name.  But currently
-there is no way to ask the archive to do this without knowing the
+dgit push needs to canonicalise the suite name.  Sometimes, dgit
+lacks a way to ask the archive to do this without knowing the
 name of an existing package.  Without --new we can just use the
 package we are trying to push.  But with --new that will not work, so
 we guess
 .B dpkg
-or use the value of this option.
+or use the value of this option.  This option is not needed with the
+default mechanisms for accessing the archive.
 .TP
 .BR -h | --help
 Print a usage summary.
@@ -646,14 +647,6 @@ We should be using some kind of vhost/vpath setup for the git repos on
 alioth, so that they can be moved later if and when this turns out to
 be a good idea.
 
-Debian Policy needs to be updated to describe the new Dgit .dsc
-field (and to specify that it is an RC bug for that field to refer
-to an unavailable commit).
-
-The method of canonicalising suite names is bizarre.  See the
-.B --existing-package
-option for one of the implications.
-
 dgit push should perhaps do `git push origin', or something similar,
 by default.