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

Re: [TSVN] TortoiseSVN no-unlock vs. svn command-line no-unlock on Windows using svn 1.2.1

From: SteveKing <steveking_at_gmx.ch>
Date: 2005-07-28 18:46:36 CEST

Philip Bondi wrote:

> My C:\Documents and Settings\philb\Application Data\Subversion\config
> file has no-unlock = yes
>
> no-unlock seems to work fine for me from the command line using:
>
> [1161] $ svn --version
> svn, version 1.2.1 (r15230)
> compiled Jul 22 2005, 10:23:40
>
> However, using TortoiseSVN it always sets my files back to read-only
> after commit.

The commit dialog in TSVN has a checkbox at the bottom for this. If you
check it, the locks are kept. If you uncheck it, the locks get released.

> This feature is important to me, so I tested carefully. Autoprops is
> less important to me, but also it does not seem to work, but I did not
> test it very carefully.

autoprops work perfectly fine in TSVN.

> The ssh = plink configuration should be spelled out more clearly in the
> documentation.

What do you think is missing in the documentation?

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 Jul 28 18:54:01 2005

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