Change Details

If the slave didn't pass a modification time (e.g. the http slave doesn't), it is set to -1 in line#672: ``` info.mtime = QDateTime::fromMSecsSinceEpoch(1000 * entry.numberValue(KIO::UDSEntry::UDS_MODIFICATION_TIME, -1), Qt::UTC); ``` This results in setting a wrong modification time for the destination file in `copyNextFile()` later on. To fix this, only set the modifcation time if it is not -1. The Qt4 version had the same check, but this got lost in the port to Qt5. BUG: 374420

If the slave didn't pass a modification time (e.g. the http slave doesn't), it was set to -1, resulting in setting a wrong modification time for the destination file in `copyNextFile()` later on because that case wasn't checked. So only set `info.mtime` when the slave actually provided a value. There's no need for further checks later in `copyNextFile()` (where `FileCopyJob::setModificationTime()` is called) because `FileCopyJob` checks for validity anyway. BUG: 374420

If the slave didn't pass a modification time (e.g. the http slave doesn't), it iit was set to -1 in line#672: ```, info.mtime = QDateTime::fromMSecsSinceEpoch(1000 * entry.numberValue(KIO::UDSEntry::UDS_MODIFICATION_TIME, -1), Qt::UTC);resulting in setting a wrong modification time for the destination file in `copyNextFile()` later on because that ``` This results in setting a wrong modification case wasn't checked. So only set `info.mtime for` when the destination file in `copyNextFile()` later onslave actually provided a value. To fix this, only set the modifcation time if it is not -1. The Qt4 version had the same check, but this got lost in the port to Qt5here's no need for further checks later in `copyNextFile()` (where `FileCopyJob::setModificationTime()` is called) because `FileCopyJob` checks for validity anyway. BUG: 374420