|author||Ian Jackson <firstname.lastname@example.org>||2017-07-08 21:11:52 +0100|
|committer||Ian Jackson <email@example.com>||2017-07-08 21:11:53 +0100|
dgit: clone multisuite works even without --no-rm-on-error.
This is slightly subtle. We need $rmonerror in cmd_clone to be cleared. cmd_clone does that only when clone itself returns. The multisuite plumbing means that currently, clone returns only in the child which set up the tree and set up the first suite. Unsetting $rmonerror there is correct because we want to keep the tree on success, and the parent will remove it if there is a later failure. (Ie, the child remains responsible for removing the tree if it itself fails.) In the parent, we get $multi_fetched==1 if not only our original clone child succeeded, but all the other fetches worked too. We are now responsible for the tree. If our final tasks are successful, again, we need not to delete the tree. Closes:#867434. Signed-off-by: Ian Jackson <firstname.lastname@example.org>
Diffstat (limited to 'debian')
1 files changed, 2 insertions, 0 deletions
diff --git a/debian/changelog b/debian/changelog
index 729985c..686c69c 100644
@@ -15,6 +15,8 @@ dgit (3.11~) unstable; urgency=medium
core.sharedRepository. Prompted by #867603.
* dgit-badcommit-fixup: Honour core.sharedRepository.
+ * dgit: clone multisuite works even without --no-rm-on-error.
* infrastructure: Cope with new git-receive-pack which has
quarantine feature: ie, work around #867702.
* test suite: Cope with git restricting ext:: protocols.