summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--NOTES4
-rw-r--r--TODO3
-rw-r--r--dgit.12
3 files changed, 6 insertions, 3 deletions
diff --git a/NOTES b/NOTES
index 192348c..984ff44 100644
--- a/NOTES
+++ b/NOTES
@@ -7,3 +7,7 @@ remote refs
local refs
refs/heads/<suite>
refs/remotes/dgit/<suite>
+
+Vcs-Dgit-Master: <commit>
+ specifies commit hash corresponding to the thing uploaded
+ optional commit hash corresponding to pristine tar??
diff --git a/TODO b/TODO
index 3f7ed25..8b13789 100644
--- a/TODO
+++ b/TODO
@@ -1,4 +1 @@
-Vcs-Dgit-Master: <commit>
- specifies commit hash corresponding to the thing uploaded
- optional commit hash corresponding to pristine tar??
diff --git a/dgit.1 b/dgit.1
index 64a03cf..d4ce176 100644
--- a/dgit.1
+++ b/dgit.1
@@ -224,6 +224,8 @@ which will make the required pseudo-merge.
If the dgit push fails halfway through, it should be restartable and
idempotent. However this is not true for the git tag operation.
+Also, it would be good to check that the proposed signing key is
+available before starting work.
dgit's handling of .orig.tar.gz is not very sophisticated. Ideally
the .orig.tar.gz could be transported via the git repo as git tags.