Closes: #935443 Signed-off-by: Ian Jackson <ijack...@chiark.greenend.org.uk> --- dgit-maint-bpo.7.pod | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/dgit-maint-bpo.7.pod b/dgit-maint-bpo.7.pod index e977d258..e776a478 100644 --- a/dgit-maint-bpo.7.pod +++ b/dgit-maint-bpo.7.pod @@ -47,6 +47,12 @@ If you use a merging backports workflow, your changelog contains entries for each previous upload to B<buster-backports>; in a rebasing workflow, it contains only the latest. +=head1 GENERAL TIPS + +The first time a package is backported +for any particular Debian release, +you will have to pass the --new option to dgit. + =head1 CHOOSING BETWEEN THE TWO WORKFLOWS If backporting involves making no (additional) changes to the upstream @@ -59,8 +65,6 @@ work on machines running Debian stable, it is advisable to choose a rebasing workflow. This ensures that dgit can automatically update the debian/patches directory without any manual intervention. -=head1 TIPS FOR A MERGING WORKFLOW - =head2 Use dgit's branches If you do not yourself upload the package to Debian unstable, it is -- 2.11.0
