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=2674d66dee14de119ff5559c52a381244362c02f;hp=cb9fe4e55adab420f3797bedcac09438ef337dc4;hb=e13fa49a03cd782945cf142fa94232a183b8e753;hpb=cb9da2c5c7e3c05adb78b682685a0fe0357958e0 diff --git a/dgit-maint-merge.7.pod b/dgit-maint-merge.7.pod index cb9fe4e5..2674d66d 100644 --- a/dgit-maint-merge.7.pod +++ b/dgit-maint-merge.7.pod @@ -202,7 +202,18 @@ this workflow. It should be skipped when debianising a new package. =head2 Existing git history using another workflow -First, dump any existing patch queue: +First, if you don't already have the git history locally, clone it, +and obtain the corresponding orig.tar from the archive: + +=over 4 + + % git clone git.debian.org:collab-maint/foo + % cd foo + % origtargz + +=back + +Now dump any existing patch queue: =over 4 @@ -232,7 +243,12 @@ To achieve this, you might need to delete I. One way to have dgit check your progress is to run B. -The first dgit push will require I<--overwrite>. +The first dgit push will require I<--overwrite>. If this is the first +ever dgit push of the package, consider passing +I<--deliberately-not-fast-forward> instead of I<--overwrite>. This +avoids introducing a new origin commit into your git history. (This +origin commit would represent the most recent non-dgit upload of the +package, but this should already be represented in your git history.) =head1 SOURCE PACKAGE CONFIGURATION @@ -284,9 +300,14 @@ A single combined diff, containing all the changes, follows. =back -Alternatively, this text could be added to README.source. However, -this might distract from more important information present in the -latter file. +If you are using the version 1.0 source package format, this text +should be added to README.source instead. The version 1.0 source +package format ignores debian/source/patch-header. + +If you're using the version 3.0 (quilt) source package format, you +could add this text to README.source instead of +debian/source/patch-header, but this might distract from more +important information present in README.source. =head1 BUILDING AND UPLOADING