Hello Bryan, > I have a user who does not have write access. I do not want them to have > write access. When > they are ready to commit changes, they must have someone come over and > approve thier > changes. This person they call over has write access. > > The setup of the read/write access is working correctly. > > What I would like is that if someone who does NOT have write access tries to > commit their > changes, that they be prompted for a login with someone who does have write > access. > > Currently, if a user who does NOT have write access reies to commit thier > changes, they get > an error. They are not given the chance to call someone over to login. > VisualSVN seems to take > one login(Stored), and will not allow someone else to commit thier changes. > > Can this be changed?
Do you really need a reviewer to come to another user's machine and *commit* from there? Why don't your users create branches or shelves for their changes? A user could create a shelve, complete his task in multiple atomic commits, notify a reviewer that it's ready for a review and if those changes are OK then a reviewer can merge them back to trunk (i.e. main development branch) from his machine. You could also use patches for peer reviewing BTW. I'd like to say that the workflow you've describes looks counterproductive and I strongly suggest considering using branching/shelving as a base for peer reviews. You might want to read these SVNBook sections: * Using Branches: https://www.visualsvn.com/support/svnbook/branchmerge/using/, * Common Branching Patterns: https://www.visualsvn.com/support/svnbook/branchmerge/commonpatterns/, * Basic Merging: https://www.visualsvn.com/support/svnbook/branchmerge/basicmerging/. Nevertheless, here is how you can workaround the authorization issue: * If you use Basic authentication then Subversion credentials cache has to be cleared first. Then the user will get a login prompt when attempting to commit. TortoiseSVN does not allow you to switch a user account on demand. See http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-settings.html#tsvn-dug-settings-saved-data. * If you use Integrated Windows Authentication, then you can use Windows Credential Manager to add another user account's credentials. See "Store passwords, certificates, and other credentials for automatic logon" Microsoft Support article at http://windows.microsoft.com/en-IN/windows7/Store-passwords-certificates-and-other-credentials-for-automatic-logon. -- With best regards, Pavel Lyalyakin VisualSVN Team -- 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.
