From d7aeeed4ce3bc05d015a84174dbfb237000d338a Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Sat, 17 Aug 2013 09:19:47 +0100 Subject: [PATCH] docs changes --- NOTES | 4 ++++ TODO | 3 --- dgit.1 | 2 ++ 3 files changed, 6 insertions(+), 3 deletions(-) diff --git a/NOTES b/NOTES index 192348ce..984ff449 100644 --- a/NOTES +++ b/NOTES @@ -7,3 +7,7 @@ remote refs local refs refs/heads/ refs/remotes/dgit/ + +Vcs-Dgit-Master: + specifies commit hash corresponding to the thing uploaded + optional commit hash corresponding to pristine tar?? diff --git a/TODO b/TODO index 3f7ed256..8b137891 100644 --- a/TODO +++ b/TODO @@ -1,4 +1 @@ -Vcs-Dgit-Master: - specifies commit hash corresponding to the thing uploaded - optional commit hash corresponding to pristine tar?? diff --git a/dgit.1 b/dgit.1 index 64a03cfd..d4ce1769 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. -- 2.30.2