Patch 2036 fix error message in clone command

Title fix error message in clone command
Superseder Nosy List bf
Related Issues
Status accepted Assigned To

Created on 2020-06-23.13:37:12 by bf, last changed 2020-07-18.13:48:57 by ganesh.

File name Status Uploaded Type Edit Remove
fix-error-message-in-clone-command.dpatch bf, 2020-06-23.13:37:11 application/x-darcs-patch
patch-preview.txt bf, 2020-06-23.13:37:11 text/x-darcs-patch
unnamed bf, 2020-06-23.13:37:11 text/plain
See mailing list archives for discussion on individual patches.
msg22112 (view) Author: bf Date: 2020-06-23.13:37:11
1 patch for repository http://darcs.net/screened:

patch 28811f853ea3244eecd88374a158f69d2a5c340f
Author: Ben Franksen <ben.franksen@online.de>
Date:   Mon Jun 22 23:11:39 CEST 2020
  * fix error message in clone command
  A command like 'ssh user@host mkdir path' can fail for lots of reasons, not
  only because the path already exists on the remote host. It is much better
  to just rely on the ssh command to report what has gone wrong.
msg22114 (view) Author: bf Date: 2020-06-23.14:58:56
I stumbled over this when testing patch2037 like this:

ben@home[1]:/tmp/bla>darcs clone bla c:/tmp/bla/z
ssh: Could not resolve hostname c: Temporary failure in name resolution
Refusing to overwrite existing file or directory.

Now it says:

ssh: Could not resolve hostname c: Temporary failure in name resolution
Cannot create remote directory '/tmp/bla/z'.
msg22171 (view) Author: ganesh Date: 2020-07-17.01:27:24
Date User Action Args
2020-06-23 13:37:12bfcreate
2020-06-23 14:28:41bfsetstatus: needs-screening -> needs-review
2020-06-23 14:58:56bfsetmessages: + msg22114
2020-07-17 01:27:24ganeshsetstatus: needs-review -> accepted-pending-tests
messages: + msg22171
2020-07-18 13:48:57ganeshsetstatus: accepted-pending-tests -> accepted