The Debian packaging of debmake-doc is maintained in git, using the merging
workflow described in dgit-maint-merge(7).  There isn't a patch queue
that can be represented as a quilt series.

Currently, debmake-doc is hosted at https://salsa.debian.org/debian/debmake-doc
and this is the best place to see change history.

Seeing the git history in the above repository should give you good
clear perspective what is in the single combined diff of this package.

Once this package is uploaded with dgit, a detailed breakdown of the changes
will available from their canonical representation - git commits in the
packaging repository.  For example, to see the changes made by the Debian
maintainer in the first upload of upstream version 1.2.3, you could use:

    % git clone https://git.dgit.debian.org/debmake-doc
    % cd debmake-doc
    % git log --oneline 1.2.3..debian/1.2.3-1 -- . ':!debian'

(If you have dgit, use `dgit clone foo`, rather than plain `git clone`.)

A single combined diff, containing all the changes, follows.

--- debmake-doc-1.17.orig/Makefile
+++ debmake-doc-1.17/Makefile
@@ -45,6 +45,10 @@ HEADXML := $(ASCIIDOC_DIR)/head.txt
 XSLT_DIR := xslt
 BASEDIR := $(CURDIR)/basedir
 TMPDIR := $(CURDIR)/tmp
+# set SOURCE_DATE_EPOCH if unset (when not called from debhelper)
+SOURCE_DATE_EPOCH ?= $(shell dpkg-parsechangelog -STimestamp)
+# date in changelog
+SOURCE_DATE := $(shell date -u +'%F %T %Z' --date=@$(SOURCE_DATE_EPOCH))
 
 # languages translated with PO files (not used now)
 LANGPO ?= ja zh-cn zh-tw de ru
@@ -345,8 +349,8 @@ $(BASEDIR)/$(MANUAL).%.epub: $(MANUAL).%
 	cp -f $(XSLT_DIR)/mimetype $(TMPDIR)/$*/mimetype
 	cp -f $(XSLT_DIR)/debian.css $(TMPDIR)/$*/OEBPS/debian.css
 	cp -f $(XSLT_DIR)/debian-openlogo.png $(TMPDIR)/$*/OEBPS/debian-openlogo.png
-	cd $(TMPDIR)/$*/ ; zip -r $@ ./
-
+	find  $(TMPDIR)/$*/ | xargs -n1 touch -d"$(SOURCE_DATE)"
+	cd $(TMPDIR)/$*/ ; zip --latest-time -r $@ ./
 
 #######################################################################
 # $ make package
--- debmake-doc-1.17.orig/asciidoc/10-prereq.txt
+++ debmake-doc-1.17/asciidoc/10-prereq.txt
@@ -69,12 +69,16 @@ NOTE: Debugging of software tends to con
 [[debian-doc]]
 === Debian documentation
 
-Please make yourself ready to read the pertinent part of the official Debian documentation together with this guide as needed to generate perfect Debian packages:
+Please make yourself ready to read the pertinent part of the latest Debian documentation to generate perfect Debian packages:
 
 * ``Debian Policy Manual''
-** ``must follow'' rules (https://www.debian.org/doc/devel-manuals#policy)
+** The official ``must follow'' rules (https://www.debian.org/doc/devel-manuals#policy)
 * ``Debian Developer's Reference''
-** ``best practice'' document (https://www.debian.org/doc/devel-manuals#devref)
+** The official ``best practice'' document (https://www.debian.org/doc/devel-manuals#devref)
+* ``Guide for Debian Maintainers'' -- this guide
+** A ``tutorial reference'' document (https://www.debian.org/doc/devel-manuals#debmake-doc)
+
+All these documents are published to https://www.debian.org using the *unstable* suite versions of corresponding Debian packages.  If you wish to have local accesses to all these documents from your base system, please consider to use techniques such as https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_tweaking_candidate_version[apt-pinning] and chroot (<<chroot>>).footnote:[It is unwise to run your base system under the pure *unstable* suite even for the development system.  Normally, most package development activities use *unstable* chroot as in <<chroot>>.  By using https://www.debian.org/doc/manuals/debian-reference/ch09.en.html#_multiple_desktop_systems[virtualization], you can test demanding situation such as the full Desktop system, network daemons, and system installer in the *unstable* suite environment even from the base system running the *stable* suite.]
 
 If this guide contradicts the official Debian documentation, the official Debian documentation is correct. Please file a bug report on the *debmake-doc* package using the *reportbug* command.
 
@@ -135,6 +139,8 @@ Thus, contributions to packages already
 
 TIP: The *wnpp-alert* command from the *devscripts* package can check for installed packages up for adoption or orphaned.
 
+TIP: The *how-can-i-help* package can show opportunities for contributing to Debian on packages installed locally.
+
 [[approaches]]
 === Contribution approaches
 
--- debmake-doc-1.17.orig/examples/debhello-0.0_build-1/step998.cmd
+++ debmake-doc-1.17/examples/debhello-0.0_build-1/step998.cmd
@@ -1 +1 @@
-realpath "$(which debmake)" | sed -e "s,/home/$(id -un),~,"
+realpath "$(command -v debmake)" | sed -e "s,/home/$(id -un),~,"
