summaryrefslogtreecommitdiff
path: root/debian/source/patch-header
diff options
context:
space:
mode:
authorB. Stack <bgstack15@gmail.com>2022-11-06 15:36:11 -0500
committerB. Stack <bgstack15@gmail.com>2022-11-06 15:36:11 -0500
commit041ad4db33c6b8e43ca615bfe785b58c68b38804 (patch)
tree276f197713b635e4d7b82c51d3600ee82bad62fb /debian/source/patch-header
parentadd man pages (diff)
downloadstackrpms-acer-chromebook-041ad4db33c6b8e43ca615bfe785b58c68b38804.tar.gz
stackrpms-acer-chromebook-041ad4db33c6b8e43ca615bfe785b58c68b38804.tar.bz2
stackrpms-acer-chromebook-041ad4db33c6b8e43ca615bfe785b58c68b38804.zip
add debian/
Diffstat (limited to 'debian/source/patch-header')
-rw-r--r--debian/source/patch-header22
1 files changed, 22 insertions, 0 deletions
diff --git a/debian/source/patch-header b/debian/source/patch-header
new file mode 100644
index 0000000..6ff0a40
--- /dev/null
+++ b/debian/source/patch-header
@@ -0,0 +1,22 @@
+The automatically generated patch puts this free form text on top of it.
+
+If you are using gbp-buildpackage(1), you probably don't need this file.
+
+If you are using dgit-maint-merge(7), please consider text as follows.
+
+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:
+
+ % git clone https://git.dgit.debian.org/foo
+ % cd foo
+ % 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.
bgstack15