[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [TSVN] Feature Request

From: SteveKing <steveking_at_gmx.ch>
Date: 2005-07-16 09:02:06 CEST

Jens Hartmann wrote:
> we start using Subversion and TortoiseSVN in our firm and some of my
> colleague
> ask for some features in TortoiseSVN.
> 1. Kill working copy after successfull comit.
> This should work as follows:
> a checkbox in the Commit-Dialog, that is normally unchecked
> when it is checked and the commit was successfull, then there had to
> appear a Messagebox: "Delete working copy" yes/no
> after clicking yes, the working copy will be deleted.

Why would you want to delete the working copy after a commit???
Honestly, I can't even imagine a reason for this!

Since I'm sure that you're the only one 'needing' this, I think it's not
too much to ask that you simple select the working copy in the explorer
and delete it manually.

> 2. Checkout externals readonly.
> This should be a checkbox in the Checkout-Dialog.
> If it is checked, all externals have to set readonly in working copy.

What do you mean with 'readonly'? If you want certain developers to
*not* have write access to specific parts of a repository, then you can
use mod_autz_svn to get fine grained access control (path based).
There's no way to mark something as 'readonly' on the client side,
especially since Subversion 1.2 now uses the file readonly flag to mark
a locked file.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Jul 16 09:02:25 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.