|author||Ian Jackson <email@example.com>||2013-10-28 02:29:03 +0000|
|committer||Ian Jackson <firstname.lastname@example.org>||2013-10-28 02:29:03 +0000|
manpage: Make discussion of --existing-package less scary. The default archive access method no longer needs it. Closes:#720171.
2 files changed, 6 insertions, 7 deletions
diff --git a/debian/changelog b/debian/changelog
index 4c799c1..4891735 100644
@@ -2,6 +2,8 @@ dgit (0.17~experimental7) experimental; urgency=low
* manpage: Remove comment in BUGS about lack of policy docs
for Dgit field, which is specified now. Closes:#720201.
+ * manpage: Make discussion of --existing-package less scary. The
+ default archive access method no longer needs it. Closes:#720171.
@@ -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.
.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
-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.
.BR -h | --help
Print a usage summary.
@@ -646,10 +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.
-The method of canonicalising suite names is bizarre. See the
-option for one of the implications.
dgit push should perhaps do `git push origin', or something similar,