On Fri, Apr 2, 2010 at 08:35, Shmigget <shmigget_at_gmail.com> wrote:
> Sure, but it's getting to be a long and diverse list. When making
> changes to your working copy you have the easy option of reverting
> your changes, but in the Repo Browser you're making changes directly
> against the repository. I discovered that one developer went into the
> Repo Browser with the intention of playing around with a possible
> reorganizing of directories, not realizing that his changes were
> taking effect. Also, and this was the situation that occurred most
> recently, we had a developer create a feature branch by going into the
> Repo Browser and creating a folder under the branches directory and
> copying files into it from the trunk. Essentially it wasn't a branch
> at all, but no one else knew that, and when it came time to merge we
> had tons of trouble.
You have a user education (or attitude) issue that will not be solved
by clamping down on the repository.
To really do what you want to do would require a modified Subversion
server - not changes on the client end.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2468816
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-04-02 18:10:13 CEST