RE: TortoiseSVN in allow-only-read-only-operations-mode

Also, for this particular scenario, it would be simpler to use the Check for Modifications feature instead of the commit dialogue.

--Craig

-----Original Message-----
From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
Sent: Wednesday, July 02, 2008 2:32 PM
To: users_at_tortoisesvn.tigris.org
Subject: Re: TortoiseSVN in allow-only-read-only-operations-mode

UnkName wrote:
> Hi,
>
> In our company we user svn by means of a in-house interface (something
> like an explorer with a whole lot of functionalities that are meant to
> ease/regulate our work - enforce code review and code ownerwhip -
> stuff like this). Unfortunately there is no feasible explore/history/
> differ on a branch (like you have in TortoiseSVN by using Commit and
> spotting the differences). Therefore, we use TSVN to see what are the
> differences in different branches (before using our internal tool to
> check-in), inspect check-in history ...
>
> My question is : can TSVN be configured to work in read-only mode such
> that to avoid accidental deletes, check-ins ...?
>
> For example: I want to see which are my differences before checking in
> (for review purposes for instance) but not to acctually be allowed to
> commit when accidentally hitting OK in the commit dialog.
> As a side mention : I am less than a neophyte in svn issues. :)

You can set up authorization rules on the server:
http://svnbook.red-bean.com/en/1.4/svn.serverconfig.httpd.html#svn.serverconfig.httpd.authz

Stefan

--
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org