On Wed, May 25, 2011 at 13:52, Aamir Khan <[email protected]> wrote: > Lets say we have a cloud named cloud PARENT. then we have two clouds CHILD-A > and CHILD-B. Now i want to sync CHILD-A with PARENT which means i will > transfer files from PARENT to CHILD-A. But lets say the process is something > which occurs frequently. Then it would be better that we maintain CLOUD-A > and PARENT as git repo and simply update git repo of CHILD-A as we want to > sync the servers. > > There won't be any Problem with this system is if CHILD-A wants to sync with > multiple PARENT repositories and i think there won't be any problem with bi > directional data flow as well. But we would have to create diff files at > time of syncing operations. > Do anybody think that there is any problem in the approach? > > -- > Aamir Khan > Indian Institute of Technology Roorkee, > Roorkee, Uttarakhand, > India , 247667 > Phone: +91 9557647357 > email: [email protected] > [email protected]
I think it's best to create diffs and commit them in the git repo every time a file gets changed, this would also be usefull for versioning and would limit merge conflicts by keeping commits small. - Robin Appelman _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
