Document that tags are in DEP-14 format, and that they are used for authenticating...

diff --git a/debian/changelog b/debian/changelog
index 81589c4955c7cc0a2718d851fa126bf07fbb238f..db433fbb866b3dae01f3386d38a6e032b8a49e7a 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,6 +2,8 @@ dgit (1.2~~) UNRELEASED; urgency=low
 
   * Fix manpage typo `dig' for `dgit'.
   * Fix manpage typo `sourcefull'.
+  * Document that tags are in DEP-14 format, and that they
+    are used for authenticating pushes.
   * Correct manpage cross-reference to point to browse.d.d.o.
 
  --

diff --git a/dgit.7 b/dgit.7
index 539ebe994ea9f7d596aef10df81721cbd1c3cbbd..a9886563eae90110f0f560bb2f73ed17fed3adf7 100644 (file)
--- a/dgit.7
+++ b/dgit.7
@@ -31,10 +31,10 @@ However, it is perfectly fine to have other branches in dgit-repos;
 normally the dgit-repos repo for the package will be accessible via
 the remote name `origin'.
 
-dgit push will also (by default) make signed tags called
+dgit push will also make signed tags called
 .BI debian/ version
-and push them to dgit-repos, but nothing depends on these tags
-existing.
+(a la DEP-14) and push them to dgit-repos.  These are used at the
+server to authenticate pushes.
 
 dgit push can operate on any commit which is a descendant of the
 current dgit/suite tip in dgit-repos.