Ian Jackson wrote on Sat, Jan 21, 2017 at 20:42:40 +0000: > This is a good direction. I now have: > > The Debian packaging of foo 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. > > 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 > first upload of upstream version 1.2.3, you could use: > > =over 4 > > % git clone https://git.dgit.debian.org/ > % cd foo > % git log --oneline 1.2.3..debian/1.2.3-1 -- . ':!debian' > > =back > > See dgit-maint-merge(7) for more information. > (If you have dgit, use dgit clone foo, > rather than plain git clone.) > > | A single combined diff, containing all the changes, follows.
For reference, the 'fossil' package (fossil is a version control system) has similar text: [[[ % head -5 debian/patches/* ==> debian/patches/series <== debian-changes ==> debian/patches/debian-changes <== This patch contains all the Debian-specific changes mixed together. The reason for doing this, rather than maintaining quilt patches, is that the Debian-specific changes are maintained as a branch in a fossil repository. To review them separately, please inspect the debian branch in http://people.debian.org/~bap/fossil.fsl ]]]
