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 the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/5b0818c3-5f72-4031-ad61-b35734fcc545n%40googlegroups.com.
