| 1 |
The automatically generated patch puts this free form text on top of it. |
| 2 |
|
| 3 |
If you are using gbp-buildpackage(1), you probably don't need this file. |
| 4 |
|
| 5 |
If you are using dgit-maint-merge(7), please consider text as follows. |
| 6 |
|
| 7 |
The Debian packaging of foo is maintained in git, using the merging workflow |
| 8 |
described in dgit-maint-merge(7). There isn't a patch queue that can be |
| 9 |
represented as a quilt series. |
| 10 |
|
| 11 |
A detailed breakdown of the changes is available from their canonical |
| 12 |
representation - git commits in the packaging repository. For example, to see |
| 13 |
the changes made by the Debian maintainer in the first upload of upstream |
| 14 |
version 1.2.3, you could use: |
| 15 |
|
| 16 |
% git clone https://git.dgit.debian.org/foo |
| 17 |
% cd foo |
| 18 |
% git log --oneline 1.2.3..debian/1.2.3-1 -- . ':!debian' |
| 19 |
|
| 20 |
(If you have dgit, use `dgit clone foo`, rather than plain `git clone`.) |
| 21 |
|
| 22 |
A single combined diff, containing all the changes, follows. |