dgit-sponsorship(7): "sample dgit push"

[dgit.git] / dgit-sponsorship.7.pod

diff --git a/dgit-sponsorship.7.pod b/dgit-sponsorship.7.pod
index e6c773044e772b53567bbf68492fb384475c44d6..40410e143cbed193ebc0edb8041a6393e5220a0d 100644 (file)
--- a/dgit-sponsorship.7.pod
+++ b/dgit-sponsorship.7.pod
@@ -75,7 +75,8 @@ Any .orig tarballs which will be needed.
 
 =item *
 
 
 =item *
 

-Any dgit --quilt= (or --gbp or --dpm) option needed
+A sample dgit push command, containing
+any dgit --quilt=, --gbp or --dpm option needed

 
 =item *
 
 
 =item *
 


@@ -136,11 +137,22 @@ handoff email.
 Some workflows involve git branches which are not natively
 dgit-compatible.
 Normally dgit will convert them as needed, during push.
 Some workflows involve git branches which are not natively
 dgit-compatible.
 Normally dgit will convert them as needed, during push.

-You need to tell your sponsor if they need to use
+
+Supply a sample "dgit push" command
+including any

 C<--gbp> (aka C<--quilt=gbp>),
 C<--dpm> (aka C<--quilt=dpm>),
 C<--gbp> (aka C<--quilt=gbp>),
 C<--dpm> (aka C<--quilt=dpm>),

-or one of the other C<--quilt=> options.
+or other C<--quilt=> option
+they need to use.
+e.g.
+
+=over 4
+
+    % dgit --gbp push

 
 

+=back
+
+=back

 
 =head1 SPONSOR WORKFLOW
 
 
 =head1 SPONSOR WORKFLOW