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

Re: [TSVN] recursive locking bug?

From: SteveKing <steveking_at_gmx.ch>
Date: 2005-06-02 19:30:55 CEST

Sean Bridges wrote:

> There seem to be some problems if I try to lock files recursively.

You can't lock files recursively.

> 1) If I select 1 directory, the "SVN Get Lock" command is not shown.

That's by design.

> 2) If I select 2 directories, I do get the "SVN Get Lock" command, but
> when the selected files are shown, the directories are selected (and
> directories cannot be locked).

That's now fixed in revision 3612.

> 3) When I de-select the directory in the selected files dialog, all the
> files in the directory are de-selected as well (this is probably the way
> it should work to be consistent with other dialogs).
> 4) If I de select the directories, reselect the files, and then try to
> lock them, I get an error message complaining that I cannot lock the
> directories (something like Error 'some directory' is not a file in
> 'some svn url'.

This is fixed in revision 3614.

> It would be really nice if I could recursively get the locks for files
> by selecting a directory.

No, sorry. I won't implement that.
Believe me, I'm only saving you from getting killed by your own
coworkers. Because if you could lock files recursively, you also could
accidentally lock the whole working copy. Imagine how your coworkers
would react ;)

Stefan

-- 
        ___
   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 Thu Jun 2 19:35:37 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.