SteveKing schrieb:
> 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.
I think i am not the only one, who has the "need" for this feature.
After finishing work on a wc you always have to delete it manually.
Possibly it is only
a "nice to have", but my colleagues ask for it.
>
>> 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.
>
> Stefan
>
I did not know that the readonly-flag is used for locking, so i thought
it were possible to set on the external file/folders on checkout.
Thanks.
---------------------------------------------------------------------
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:40:07 2005