| 2017-01-29 22:23:30 |
NaSH |
description |
on nemo 3.22, all operations from/to a sftp share don't keep the mtime (modification timestamp)
it's annoying, cause i think it's the convenient way to mount a temporary network share, advertised via avahi. (well... at least for a home network)
if you open a terminal, in this mounted network, and move a file, (from here, to your home directory) the mtime i kept.
but not if you do a copy.
so i guess the normal behaviour should be that a move, keep the mtime, and a copy, use the current time.
(on a mounted windows share, a copy keep the mtime. So i guess there's a problem here. |
on nemo 3.22, all operations from/to a sftp share don't keep the mtime (modification timestamp)
it's annoying, cause i think it's the convenient way to mount a temporary network share, advertised via avahi. (well... at least for a home network)
if you open a terminal, in this mounted network, and move a file, (from here, to your home directory) the mtime i kept.
but not if you do a copy.
so i guess the normal behaviour should be that a move, keep the mtime, and a copy, use the current time.
(on a mounted windows share, a copy keep the mtime. So i guess there's also problem here.) |
|
| 2017-01-29 22:24:51 |
NaSH |
description |
on nemo 3.22, all operations from/to a sftp share don't keep the mtime (modification timestamp)
it's annoying, cause i think it's the convenient way to mount a temporary network share, advertised via avahi. (well... at least for a home network)
if you open a terminal, in this mounted network, and move a file, (from here, to your home directory) the mtime i kept.
but not if you do a copy.
so i guess the normal behaviour should be that a move, keep the mtime, and a copy, use the current time.
(on a mounted windows share, a copy keep the mtime. So i guess there's also problem here.) |
on nemo 3.22, all operations from/to a sftp share don't keep the mtime (modification timestamp)
it's annoying, cause i think it's the convenient way to mount a temporary network share, advertised via avahi. (well... at least for a home network)
if you open a terminal, in this mounted network, and move a file, (from here, to your home directory) the mtime i kept.
but not if you do a copy.
so i guess the normal behaviour should be that a move, keep the mtime, and a copy, use the current time.
(on a mounted windows share, with nemo, a move keep the mtime, but a copy also keep the mtime. So i guess there's also problem here.) |
|
