Can you fix it for me ? Ravi
On Monday, January 28, 2013, Giuseppe Scrivano <[email protected]> wrote: > indeed, that is a bug. > > this line in the url_file_name function seems the cause: > > if ((opt.noclobber || opt.always_rest || opt.timestamping || opt.dirstruct) > && !(file_exists_p (fname) && !file_non_directory_p (fname))) > > the last condition should not be used when the protocol is FTP, it seems > a workaround for some broken http servers. > > Giuseppe > > > > > Ravi Sharma <[email protected]> writes: > >> I do see Unrecognized permissions for <Path to directory>/<Directory Name>.1. for some of the directories in debug output. >> >> does anyone has any idea why would we get some thing like this when we have this directory for both local and remote servers??? >> >> Thanks >> >> On Sun, Jan 27, 2013 at 1:49 PM, Ángel González <[email protected]> wrote: >> >> On 27/01/13 22:33, Giuseppe Scrivano wrote: >> > sorry now I see what you mean... >> > >> > I am not very familiar with the FTP implementation but I am afraid it >> > will need some changes in the way it works now and avoid any operation >> > in the directory after you set the mtime. Can anyone with more >> > experience in the FTP implementation confirm this? >> > >> > Cheers, >> > Giuseppe >> >> Why not move the action of setting of mtime point until after leaving >> the directory? >
