It's UWAweek 10 (1st semester, week 2)


This forum is provided to promote discussion amongst students enrolled in CITS2002 Systems Programming.
Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.
Displaying selected article
Showing 1 of 1168 articles.
Currently 1 other person reading this forum.

 UWA week 40 (2nd semester, week 10) ↓
SVG not supported

Login to reply

12:55pm Mon 2nd Oct, Christopher M.

"Jacob Read" <23*7*9*6@s*u*e*t*u*a*e*u*a*> wrote:
> If the program is syncing both files and directories (so it's being called recursively), what happens if in one directory a file is called "thing1", but in another directory, a sub-directory is called "thing1" as well. Obviously these can't be directly synced with each other, as you would do with files by just comparing last edited time. And they can't both be synced separately, as files and directories can't be named the same thing. What should occur in this circumstance? Should the most recent version just override the other and delete the other occurence? So if the file with the name "thing1" was made most recently, the directory would be deleted. Or would this be skipped somehow, so "thing1" just isn't synced as a file or directory?
Nothing gets deleted in the project. We are syncing files, either from the top-level directories or sub-directories if using -r. We are not actually syncing directories, or their contents, but (as a side-effect) will need to create corresponding directories when syncing files.

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  5:07AM Sep 06 2023
Privacy policy