chiark / gitweb /
dgit(1): Entry for build-source recommends using push-source
authorSean Whitton <spwhitton@spwhitton.name>
Sat, 30 Dec 2017 11:07:42 +0000 (11:07 +0000)
committerIan Jackson <ijackson@chiark.greenend.org.uk>
Sun, 7 Jan 2018 19:31:59 +0000 (19:31 +0000)
If the user invokes build-source because they are going to upload,
they should use push-source rather than push to benefit from the
additional safety check that the upload is actually source-only.

Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
Acked-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
dgit.1

diff --git a/dgit.1 b/dgit.1
index 4f1479884d1d73b57019ad50d75917185a531496..6d46b20a4c7887158a567a89f90a82db53176e0a 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -127,7 +127,8 @@ The output is left in
 and
 .IR package \fB_\fR version \fB_source.changes\fR.
 
 and
 .IR package \fB_\fR version \fB_source.changes\fR.
 
-Tagging, signing and actually uploading should be left to dgit push.
+Tagging, signing and actually uploading should be left to dgit
+push-source, or dgit push.
 .TP
 .B dgit clean
 Cleans the current working tree (according to the --clean= option in
 .TP
 .B dgit clean
 Cleans the current working tree (according to the --clean= option in