manpage: Remove comment in BUGS about lack of policy docs for Dgit field, which is...

[dgit.git] / dgit.1

diff --git a/dgit.1 b/dgit.1
index 75a43a390d7cec1dc955b311e6360fd09048c8fc..5c171ed78dd94dd34501b0a340e55dfdcca7e902 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -646,10 +646,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.
@@ -700,10 +696,6 @@ There should be an option which arranges for the `3.0 (quilt)'
 autocommit to not appear on your HEAD, but instead only in the
 remote tracking suite branch.
 
-There should at the very least be some advice in the manpage about how
-to use dgit when the signing key is not available on the same machine
-as the build host.
-
 The option parser requires values to be cuddled to the option name.
 
 dgit assumes knowledge of the archive database.  (The information dgit