docs changes

diff --git a/NOTES b/NOTES
index 192348ce4a75ba256c99cbb22aa5fa5e9098ebdb..984ff4490129ba5149786168a10e2dcf688b6391 100644 (file)
--- 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 3f7ed2565541838f03251eb405d6931dbaf7175b..8b137891791fe96927ad78e64b0aad7bded08bdc 100644 (file)
--- 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 64a03cfd6bc291c128a66b93636d4a41e2c289a2..d4ce17693eb93a2b08a9c9da92538c545bae32db 100644 (file)
--- 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.