summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2017-01-25 08:08:55 -0700
committerSean Whitton <spwhitton@spwhitton.name>2017-01-25 08:08:55 -0700
commite9307720120c5d030ab4855d8b044029af7cb8e0 (patch)
tree94605aeffca2a7838ba7e1fc8be6021e49436a6b
parent3289726f729507e154c92883a728f88bcfd31074 (diff)
downloadkeysafe-e9307720120c5d030ab4855d8b044029af7cb8e0.tar.gz
foo->keysafe in patch header
-rw-r--r--debian/patches/debian-changes12
-rw-r--r--debian/source/patch-header10
2 files changed, 11 insertions, 11 deletions
diff --git a/debian/patches/debian-changes b/debian/patches/debian-changes
index a62110e..e3dfbf5 100644
--- a/debian/patches/debian-changes
+++ b/debian/patches/debian-changes
@@ -1,17 +1,17 @@
-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.
+The Debian packaging of keysafe 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/
- % cd foo
+ % git clone https://git.dgit.debian.org/keysafe
+ % cd keysafe
% 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`.)
+(If you have dgit, use `dgit clone keysafe`, rather than plain `git clone`.)
A single combined diff, containing all the changes, follows.
--- keysafe-0.20170122.orig/keysafe.init
diff --git a/debian/source/patch-header b/debian/source/patch-header
index 0dacc46..5607b6b 100644
--- a/debian/source/patch-header
+++ b/debian/source/patch-header
@@ -1,6 +1,6 @@
-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.
+The Debian packaging of keysafe 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
@@ -8,9 +8,9 @@ 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/
- % cd foo
+ % cd keysafe
% 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`.)
+(If you have dgit, use `dgit clone keysafe`, rather than plain `git clone`.)
A single combined diff, containing all the changes, follows.