On Aug. 3, 2012, 8:48 a.m., David Faure wrote:
I'm not sure this makes sense. You drag-n-drop a symlink called link to a
file called target from fish://myhost to your local $HOME, and you end up
with a broken symlink, given that target is nowhere to be found?
The logic of the test
On Aug. 3, 2012, 8:49 a.m., David Faure wrote:
Actually we need to test both source and destination to check if their
protocols support symlink creation.
Haha, if we're copying a symlink, then obviously the source protocol
supports symlinks, otherwise it wouldn't be there in the
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/105563/
---
(Updated Aug. 5, 2012, 12:39 p.m.)
Review request for KDE Runtime and
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/105563/
---
(Updated Aug. 5, 2012, 1:25 p.m.)
Review request for KDE Runtime and
On Friday 03 August 2012, David Faure wrote:
I'm not sure this makes sense. You drag-n-drop a symlink called link to a
file called target from fish://myhost to your local $HOME, and you end
up with a broken symlink, given that target is nowhere to be found?
Would it be relevant to offer the
On Aug. 3, 2012, 8:48 a.m., David Faure wrote:
I'm not sure this makes sense. You drag-n-drop a symlink called link to a
file called target from fish://myhost to your local $HOME, and you end up
with a broken symlink, given that target is nowhere to be found?
The logic of the test
