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

Re: Error message nitpick

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-05-02 18:13:26 CEST

On May 2, 2005, at 10:45 AM, Lübbe Onken wrote:

> Hi Folks,
> we have got several error messages concerning the working copy that
> use the term 'locked' but have nothing to do with locking files.
> From the po file:
> 'Working copy not locked; this is probably a bug, please report'
> I also remember seeing (haven't found in current po file, so probably
> obsolete)
> 'Working copy locked, please run cleanup'
> I think that these cases of using 'locked' will confuse users.

Those errors are as old as svn itself. The problem is that we now have
four definitions of 'lock':

   * working-copy 'locks', used to get exclusive access to a working
copy dir (used by libsvn_wc),

   * repository BDB 'locks', a resource that BDB can run out of,

   * repository FSFS 'write lock', used by libsvn_fs_fs to get exclusive
access when doing a write operation,

   * repository locks -- the new svn 1.2 feature for reserving access to
imaginary files.

I'm not sure what we can do to disambiguate these error messages or

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 2 18:15:37 2005

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

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