Open GoogleCodeExporter opened 9 years ago
Hi Cameron,
somehow I can't get what the problem is. What do you mean by "have deleted the
working copy"? Do you mean source or destination?
What do you mean by "If there was an option to not sync delete"? FileSync
should not delete target files if source files were deleted?
This is be possible to implement, but then you will end up in the situation
where you have lot of garbage on the "remote" part. What you would do then?
My idea for FileSync is that it works as simple as possible, so that anyone can
understand the result. This means, the target folder should ideally be just a
mirror of the source. For all "sophisticated" workflows sophisticated tools
should be used, for example version control systems like git etc.
So while technically possible, I doubt I will implement it. You can try to
convince me. BTW a patch with attached junit tests would definitely help :-)
P.S.
The title of your report seems to be misleading: did you mean "Option to *not*
delete remote file on sync"?
Regards,
Andrey
Original comment by iloveeclipse
on 31 Aug 2014 at 9:08
Original issue reported on code.google.com by
cameron....@gmail.com
on 27 Aug 2014 at 9:47