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

On Wed, Oct 09, 2002 at 08:18:16PM +0100, Philip Martin wrote:
> Jeff Putsch <putsch@mxim.com> writes:
>
> > On Wed, Oct 09, 2002 at 06:31:43PM +0100, Philip Martin wrote:
> > > Don't you get an error at this stage? Something like
> > >
> > > svn: Working copy not locked
> > > svn: directory not locked (foo)
> >
> Storing auth info is usually done as a
> last pass over the working copy tree, and it is that pass that is
> generating the error.

It seems to me that during an 'svn update' the auth information is
known, otherwise the comparison and pull from the repository would not
work. So why does the 'svn update' give that error. It seems to me it
has the information it needs to store the auth information. If 'svn
update' stored the information then later 'svn status' commands
wouldn't need to.

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