docs: dgit(7): Update for change to dgit push-*

We speak here of "dgit push-*" when we mean "push-source or push-built
or push".

Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>

1 files changed, 10 insertions, 9 deletions

diff --git a/dgit.7 b/dgit.7
index 4144ed6..bf805a5 100644
--- a/dgit.7
+++ b/dgit.7
@@ -47,7 +47,7 @@ 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 make signed tags called
+dgit push-* will also make signed tags called
 .BI archive/debian/ version
 (with version encoded a la DEP-14)
 and push them to dgit-repos.  These are used at the
@@ -55,7 +55,7 @@ server to authenticate pushes.
 
 Uploads made by dgit contain an additional field
 .B Dgit
-in the source package .dsc.  (This is added by dgit push.)
+in the source package .dsc.  (This is added by dgit push-*.)
 This specifies: a commit (an ancestor of the dgit/suite
 branch) whose tree is identical to the unpacked source upload;
 the distro to which the upload was made;
@@ -89,7 +89,7 @@ but may be ahead of it if uploads have been done without dgit.
 The archive tracking view is always fast forwarding within
 each suite.
 
-dgit push can operate on any commit which is a descendant of
+dgit push-* can operate on any commit which is a descendant of
 the suite tracking branch.
 
 dgit does not make a systematic record of
@@ -100,7 +100,7 @@ The
 orig tarballs are downloaded (by dgit clone) into the parent
 directory, as with a traditional (non-gitish) dpkg-source workflow.
 You need to retain these tarballs in the parent directory for dgit
-build and dgit push.
+build and dgit push-*.
 (They are not needed for purely-git-based workflows.)
 
 dgit repositories could be cloned with standard (git) methods.
@@ -403,7 +403,7 @@ into a dgit branch.
 
 When a splitting quilt mode is selected
 dgit build commands and
-dgit push
+dgit push-*
 will, on each invocation,
 convert the user's HEAD into the dgit view,
 so that it can be built and/or uploaded.
@@ -419,11 +419,11 @@ regardless of the quilt mode,
 any dgit-generated pseudomerges
 and any quilt fixup commits
 will appear only in the dgit view.
-dgit push
+dgit push-*
 will push the dgit view to the dgit
 git server.
 The dgit view is always a descendant of the maintainer view.
-dgit push will also make a maintainer view tag
+dgit push-* will also make a maintainer view tag
 according to DEP-14
 and push that to the dgit git server.
 
@@ -449,8 +449,9 @@ in the source tarball, but some people prefer not to have it present
 in the git view of their project.
 
 dgit requires that the source package unpacks to exactly the same
-files as are in the git commit on which dgit push operates.  So if you
-just try to dgit push directly from one of these extra-clean git
+files as are in the git commit on which dgit push-* operates.
+So if you
+just try to dgit push-* directly from one of these extra-clean git
 branches, it will fail.
 
 As the maintainer you therefore have the following options: