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

Re: the last M4 (M5) bugs

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2001-10-18 22:11:36 CEST

Greg Stein <gstein@lyra.org> writes:

> > Specifically, the "working" revision of the directory needs to be
> > sent in the PROPPATCH request body. mod_dav_svn can then look at
> > the node-rev-id of the latest version of the directory, see what
> > revision it was *created* in (it's part of the skel), and compare
> > it to the "working" revision from the client. It's an easy
> > out-of-dateness check that requires no undeltifying, and is a
> > foreshadowing of the commit-system of the future. :-)
>
> No. You cannot send the working revision in the body. Blech.
>
> A CHECKOUT is performed before doing the PROPPATCH. That checkout uses the
> version url from when the directory was initially checked out. The system
> should have punted on that initial CHECKOUT. If it didn't, then the question
> is "why?"

The "system"? Do you mean client, or server?

How could either system know to punt?

I mean, directory CHECKOUTS are done all the time -- not just before
proppatching a directory, but anytime we edit a file too (the file's
parent is checked out first.)

So -- if the server receives a PROPPATCH on a directory, is there any
way mod_dav_svn can "recall" the vsn_url that was used to initially
checkout the directory? If so, it can examine the vsn_url and reject
the PROPPATCH as out-of-date.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:45 2006

This is an archived mail posted to the Subversion Dev mailing list.