diff options
author | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2013-08-17 09:19:47 +0100 |
---|---|---|
committer | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2013-08-17 09:19:47 +0100 |
commit | d7aeeed4ce3bc05d015a84174dbfb237000d338a (patch) | |
tree | 541afc1cb2ef202b4a5d26677de2f8b3fc415939 | |
parent | 2641d83f454808b2a97c32df5556c50da31660b3 (diff) |
docs changes
-rw-r--r-- | NOTES | 4 | ||||
-rw-r--r-- | TODO | 3 | ||||
-rw-r--r-- | dgit.1 | 2 |
3 files changed, 6 insertions, 3 deletions
@@ -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?? @@ -1,4 +1 @@ -Vcs-Dgit-Master: <commit> - specifies commit hash corresponding to the thing uploaded - optional commit hash corresponding to pristine tar?? @@ -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. |