bugfixes from testing, for recent changes

[dgit.git] / dgit.1

diff --git a/dgit.1 b/dgit.1
index 14b7d1ed42e88973a68e841557390e39a867db3c..1f5fd84fca843e47075c10bb2c4a71fc1d530276 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -32,6 +32,10 @@ as
 .B dgit-repos
 which lives outside the Debian archive (currently, on Alioth).
 
+The usual workflow is: 1. clone or fetch; 2. make and commit changes
+in git as desired; 3. run dgit build or dgit sbuild, or generate the
+source and binary packages for upload some other way; 4. do
+pre-upload tests of the proposed upload; 5. run dgit push.
 .TP
 \fBdgit clone\fR \fIpackage\fP [\fIsuite\fP] [\fB./\fP\fIdir|\fB/\fP\fIdir]
 Consults the archive and dgit-repos to construct the git view of
@@ -317,7 +321,8 @@ Can be repeated as necessary.
 .BI -C changesfile
 Specifies the .changes file which is to be uploaded.  By default
 dgit push looks for single .changes file in the parent directory whose
-filename suggests it is for the right package and version.
+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