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

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

From: Philip Bondi <pjbondi_at_SystemDatabase.com>
Date: 2005-07-28 16:27:06 CEST

Hello to all:

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

Copyright (C) 2000-2005 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet
(http://www.Collab.Net/).

The following repository access (RA) modules are available:

* ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol.
   - handles 'http' scheme
   - handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network
protocol.
   - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
   - handles 'file' scheme

However, using TortoiseSVN it always sets my files back to read-only after
commit.

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.

I'm accessing my SVN repo using PuTTY 0.58. So my C:\Documents and
Settings\philb\Application Data\Subversion\config also has ssh = plink

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

-- 
Philip Bondi, home: +1 -416 621.9177, pjbondi@SystemDatabase.com
               cell: +1 -416 540-2869
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Jul 28 16:50:48 2005

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