summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIan Jackson <ijackson@chiark.greenend.org.uk>2019-09-05 16:50:28 +0100
committerIan Jackson <ijackson@chiark.greenend.org.uk>2019-09-14 20:29:30 +0100
commit506e117246da9f49499dcd8c97993316c79b4a66 (patch)
tree2a819bbce50999793a33dd2588a293fa0818a310
parent5b3766dcfcd3984ed864a0334f02deb5999a8b2a (diff)
dgit-maint-bpo(7): Mention occasional need for --new
Closes: #935443 Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
-rw-r--r--dgit-maint-bpo.7.pod6
1 files changed, 6 insertions, 0 deletions
diff --git a/dgit-maint-bpo.7.pod b/dgit-maint-bpo.7.pod
index e977d25..86372dd 100644
--- a/dgit-maint-bpo.7.pod
+++ b/dgit-maint-bpo.7.pod
@@ -8,6 +8,12 @@ This document describes elements of a workflow for using B<dgit> to
maintain an official Debian backport. We do not assume that whoever
uploads the package to Debian unstable is using B<dgit>.
+=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 TERMINOLOGY
Let the I<master> branch contain the packaging history uploaded to