X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=dgit-maint-merge.7.pod;h=dc5bfa34043dd1dac121f416b3d2bc3ce444c0ad;hp=62c8c1f82aa275f4c77e82389c051f52362b1250;hb=b4adde108b83933d435bf2a494413c9c9deaa23a;hpb=ff2ebaf0a41a3edc8f71f778082f0cb3d34610e0

diff --git a/dgit-maint-merge.7.pod b/dgit-maint-merge.7.pod
index 62c8c1f8..dc5bfa34 100644
--- a/dgit-maint-merge.7.pod
+++ b/dgit-maint-merge.7.pod
@@ -187,6 +187,7 @@ this workflow.  It should be skipped when debianising a new package.
 
     % dgit clone foo
     % cd foo
+    % git remote add -f upstream https://some.upstream/foo.git
 
 =back
 
@@ -201,6 +202,14 @@ First, dump any existing patch queue:
 
 =back
 
+Then make new upstream tags available:
+
+=over 4
+
+    % git remote add -f upstream https://some.upstream/foo.git
+
+=back
+
 Now you simply need to ensure that your git HEAD is dgit-compatible,
 i.e., it is exactly what you would get if you ran B<dpkg-buildpackage
 -i\.git/ -I.git -S> and then unpacked the resultant source package.
@@ -209,7 +218,7 @@ To achieve this, you might need to delete
 I<debian/source/local-options>.  One way to have dgit check your
 progress is to run B<dgit build-source>.
 
-The dgit push will require I<--overwrite>.
+The first dgit push will require I<--overwrite>.
 
 =head1 SOURCE PACKAGE CONFIGURATION