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

Re: HTTP authentication vs. --username and --password

From: Peter Davis <peter_at_pdavis.cx>
Date: 2002-07-22 04:17:48 CEST

On Sunday 21 July 2002 19:02, Ben Collins-Sussman wrote:
> > <entry
> > committed-rev="1"
> > name="svn:this_dir"

Something I just realized, sorry that it is totally unrelated:

$ svn mkdir 'svn:this_dir'

svn_error: #21051 : <Unmergeable scheduling requested on an entry>
  fold_state_changes: Entry 'svn:this_dir' already under revision control

..... probably will never come up in real life, but I have always had an
aversion to magic strings.

> > committed-date="2002-07-14T10:44:21.733385Z"
> > url="http://username@server/repos/path..."
> > last-author="username"
> > kind="dir"
> > revision="N"/>
> These are totally unrelated bits of information. The stuff in the
> .svn/auth/ area is a cached password that is used to respond to http
> challenges.

Sorry for any confusion. I was referring only to


and whether that is duplicating the stuff in auth/ (or vice versa).

> I don't how you got 'username' into that 'last-author' attribute
> there... is that indeed the name of the user that created revision 1?

Yes. Well kind of. In the original entries from which I took this example,
the username was 'pdavis' (me). I just replaced that with 'username' when I
also replaced the real name of my server with 'server'.

Peter Davis
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 22 04:18:24 2002

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.