dgit-maint-debrebase(7): improve "Upstream branches"

Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>

diff --git a/dgit-maint-debrebase.7.pod b/dgit-maint-debrebase.7.pod
index 6d14c0bea82bde8f97dada747ebcce8d3e95ff2b..e78f5f28eaf220ae2b0f3650149c710ec81bd9cf 100644 (file)
--- a/dgit-maint-debrebase.7.pod
+++ b/dgit-maint-debrebase.7.pod
@@ -567,14 +567,15 @@ than sending files from I<debian/patches>.
 
 =head2 Upstream branches
 
-Except in the case where upstream releases only tarballs, we do not
-maintain a separate 'upstream' branch (unless you also happen to be
-involved in upstream development).  We work with upstream tags rather
-than any branches, except temporary branches used to prepare patches
-for forwarding upstream, for example.
-
-The thought behind this is that from Debian's point of view, upstream
-releases are immutable points in history, better represented by tags.
+Except in the case where upstream releases only tarballs, or we
+require DFSG filtering, we do not maintain a separate 'upstream'
+branch (unless you also happen to be involved in upstream
+development).  We work with upstream tags rather than any branches
+(except temporary branches used to prepare patches for forwarding
+upstream, for example).
+
+The idea here is that from Debian's point of view, upstream releases
+are immutable points in history, and so better represented by tags.
 
 =head2 The first ever dgit push