chiark
/
gitweb
/
~ianmdlvl
/
dgit.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
remove empty TODO
[dgit.git]
/
dgit.1
diff --git
a/dgit.1
b/dgit.1
index 06a7ee94e4ee78e0e2888a1ce5a143b7378b899e..d4ce17693eb93a2b08a9c9da92538c545bae32db 100644
(file)
--- a/
dgit.1
+++ b/
dgit.1
@@
-222,6
+222,11
@@
branch back into a rebasing patch stack, and a `force' option to dgit
push (perhaps enabled automatically by a note left by rebase-prep)
which will make the required pseudo-merge.
push (perhaps enabled automatically by a note left by rebase-prep)
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.
Doing this is made more complicated by the possibility of a `3.0
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.
Doing this is made more complicated by the possibility of a `3.0