> From: Steven Bakke [mailto:steven.bakke_at_amd.com]
> Sent: 01 July 2008 13:42
>
> On Jul 1, 2008, at 7:53 AM, Giulio Troccoli wrote:
>
> > From the Subversion Book (both for 1.4.4 and 1.5):
> >
> > "[svn-commit] searches the working copy (or list of targets, if you
> > provide such a list) for local modifications and sends all the lock
> > tokens it encounters during this walk to the server as part of the
> > commit transaction. After the commit completes successfully, all of
> > the
> > repository locks that were mentioned are released-even on files that
> > weren't committed. This is meant to discourage users from being
sloppy
> > about locking or from holding locks for too long."
>
> FYI, for this behavior there is either a bug in subversion 1.4.x (and
> presumeably
> 1.5.x) or this documentation is incorrect. I've found that if I try
> to commit
> a file that is locked but without local modifications, it won't unlock
> that file. I
> assume this is because it only auto-unlocks files that are modified.
>
I have just test this and it does what the book said, at least with
1.4.4. If however, I specify a list of files to commit, then the locks
of the other files are preserved.
I attached the script I have been using.
Linedata Services (UK) Ltd
Registered Office: Bishopsgate Court, 4-12 Norton Folgate, London, E1 6DB
Registered in England and Wales No 3027851 VAT Reg No 778499447
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
- application/octet-stream attachment: lock-test
Received on 2008-07-01 15:18:58 CEST