diff options
author | louie <louie@example.com> | 2023-09-28 16:39:22 -0400 |
---|---|---|
committer | louie <louie@example.com> | 2023-09-28 16:39:22 -0400 |
commit | 8c789eea182874dbc9234ea7d41971a2181617e4 (patch) | |
tree | eca8d49813a052bb7222ff28cd5b16893e930b1b /debian/source/patch-header | |
parent | 14112852265ba6f6b1526b78a52c1367d57134e2 (diff) |
Create rudimentary debian directory
Diffstat (limited to 'debian/source/patch-header')
-rw-r--r-- | debian/source/patch-header | 22 |
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. |