Hi, I'm very new to Subversion and VisualSVN so I'm not sure if this is even possible.
I'd like to have a central share for all our Powershell scripts (there are currently hundreds of scripts running on countless servers in the organisation) where all the scripts we use are executed from These scripts would be in a shared folder on the server (let's called it \\SERVER1\Scripts$). The only people who should be able to directly modify files in there are designated ScriptAdmins (I guess I can use NTFS permissions for that). Now, what I would like to be able to do is to have something similar to the Advanced Group Policy Managment functionality in Windows Server 2008 in that anyone who wants to modify a script in that shared folder has to go via some form of Subversion/Source Control So, they would use, say, TortoiseSVN client to check out a script, modify it and then Commit the change to the repository and those changes would then be applied to the original source file in the shared folder, Scripts$. In my testing, however, the committed changes are NOT replicated to the Scripts$ share. I presume I am simply misunderstanding how subversion works? Is there any way to have this scenario? -- You received this message because you are subscribed to the Google Groups "VisualSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to visualsvn+unsubscr...@googlegroups.com. To post to this group, send email to visualsvn@googlegroups.com. Visit this group at http://groups.google.com/group/visualsvn. For more options, visit https://groups.google.com/d/optout.
