Re: BUG? ... 'svn update' does not save authentication information

On Wed, Oct 09, 2002 at 06:31:43PM +0100, Philip Martin wrote:
> Jeff Putsch <putsch@mxim.com> writes:
> > 5 have user1 update their working copy.
>
> Don't you get an error at this stage? Something like
>
> svn: Working copy not locked
> svn: directory not locked (foo)

Yes I get that error. Wish it would go away. The data seems to have been
pulled from the repository correctly.

I've updated to r3338 and still get that error. I also get that error
when trying to do "svn st -u some/path", while "svn st -u" works just fine.

Jeff.

-- 
Jeff Putsch                       Email: putsch@mxim.com
Maxim Integrated Products        Office: (503)547-2037
High Frequency CAD Engineering
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org