Yh TSVN fails in the onedrive environment. Some commands disappear in TSVN and onedrive sync fails in some cases. Locking files before editing is the best option we have so far.
Regards, On Sun, Nov 19, 2023 at 11:09 PM Ömer GÜNDÜZ <omer.gnd...@gmail.com> wrote: > 1) "I would imagine that OneDrive will encounter conflicts on the > databases and files within the .svn administrative folder. That is probably > a BAD idea." > Actually, I have concerns about this too. However, I will give it a try > and see the results on a relatively easy project. > 2) "The Subversion approach to non-mergeable binary files is to use > locking, see the description of SVN lock in the SVN book [1]. This can be > enforced by the svn:needs-lock property, see [2]" > Lock option is also on the table but I am not in favor of letting only one > person at each time. > > Thank you very much, Daniel. I will let you know about my hybrid (TSVN + > Onedrive) approach. > > On Sun, Nov 19, 2023 at 10:28 PM Daniel Sahlberg via TortoiseSVN-dev < > tortoisesvn-dev@googlegroups.com> wrote: > >> lördag 18 november 2023 kl. 22:13:20 UTC+1 skrev Ömer GÜNDÜZ: >> >> Hello again, >> Thank you very much for your answer, Daniel. >> After facing challenges in finding an effective conflict resolution >> method, I have opted to utilize my workspace within the OneDrive folder. >> This approach allows us to collaborate on a shared file, with the file >> owner handling the commits for the team. I am curious if there are >> potential issues associated with this method. Has anyone encountered >> challenges using this approach (i.e. TSVN icons will not show up)? >> Additionally, do you recommend employing TSVN within the OneDrive >> environment? >> Thank you in advance for your help >> >> >> Just so I understand, have you put the complete working copy on OneDrive? >> I have not tried, but if several persons performing SVN actions on that >> folder, I would imagine that OneDrive will encounter conflicts on the >> databases and files within the .svn administrative folder. That is probably >> a BAD idea. >> >> The Subversion approach to non-mergeable binary files is to use locking, >> see the description of svn lock in the svn book [1]. This can be enforced >> by the svn:needs-lock property, see [2]. That way you don't have any merge >> conflicts, at the cost of only one person being able to work on a >> particular file at each time. >> >> Kind regards, >> Daniel >> >> [1] https://svnbook.red-bean.com/en/1.7/svn.advanced.locking.html >> [2] >> https://svnbook.red-bean.com/en/1.7/svn.ref.properties.html#svn.ref.properties.versioned-props >> >> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "TortoiseSVN-dev" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/tortoisesvn-dev/O761YqWwoNw/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> tortoisesvn-dev+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/tortoisesvn-dev/5b0818c3-5f72-4031-ad61-b35734fcc545n%40googlegroups.com >> <https://groups.google.com/d/msgid/tortoisesvn-dev/5b0818c3-5f72-4031-ad61-b35734fcc545n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/CAFd1np74FaHRWfYC1%2B5SJ2XvY3Yce3QiGdLJaxFXUi9U37nkCQ%40mail.gmail.com.
