On 9/2/07, Glen Barber <hexidigital@gmail.com> wrote:
> Quoting Andy Levy:
> > On 9/2/07, Glen Barber <hexidigital@gmail.com> wrote:
> > > Quoting Mark Reibert:
> > > > Is there anything else you can provide regarding the client side of the
> > > > problem? Have you tried tracking your steps in a parallel working copy
> > > > to make sure the commits are getting into the repo?
> > >
> > > Well, it seems I may have found what I was doing incorrectly. I do not
> > > know if this is typical behavior for SVN, because I have never used
> > > locks before. Here's what I have to do to get it to work:
> > > svn lock myfile.doc -m "whatever my reason is"
> > > svn update
> > > svn commit -m "blah blah"
> > > (this is where I was getting lost earlier -- is it
> > > necessary to update after locking? Otherwise, after I edit and commit,
> > > I receive the same errors as before.)
> >
> > I normally update, lock, edit, then commit. Hasn't failed for me.
> >
> That was my understanding from the book. I wonder if it's a TortoiseSVN
> thing.
Doubtful. I do it with both TSVN and Win32 CLI client. I have yet to
have the trouble you describe.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Sep 2 16:52:58 2007