Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
=head2 Sample text for debian/source/patch-header
=head2 Sample text for debian/source/patch-header
-It is a good idea to explain how a user can obtain a break down of the
+It is a good idea to explain how a user can obtain a breakdown of the
changes to the upstream source:
=over 4
The Debian packaging of foo is maintained in git,
using the merging workflow described in dgit-maint-merge(7).
changes to the upstream source:
=over 4
The Debian packaging of foo is maintained in git,
using the merging workflow described in dgit-maint-merge(7).
-An automatically generated representation of the Debian changes follows.
+There isn't a patch queue that can be represented as a quilt series.
-A detailed break down of these changes is available from their
+A detailed breakdown of the changes is available from their
canonical representation -
git commits in the packaging repository.
For example, to see the changes made by the Debian maintainer in the
canonical representation -
git commits in the packaging repository.
For example, to see the changes made by the Debian maintainer in the
(If you have dgit, use dgit clone foo,
rather than plain git clone.)
(If you have dgit, use dgit clone foo,
rather than plain git clone.)
+A single combined diff, representating all the changes, follows.
+
=back
Alternatively, this text could be added to README.source. However,
=back
Alternatively, this text could be added to README.source. However,