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

Re: Locking non-existent paths. Time to discuss.

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2005-03-21 17:07:25 CET

Julian Reschke <julian.reschke@gmx.de> writes:

> > LOCK nonexistentURL
> ...would create an empty locked resource...
> > PUT 0-byte-file
> ...would check it out and update it with 0 byte content...
> > PUT real-file
> ...would update the content again...
> ...would unlock it and check it back in (so a single version is created).
> But this requires the server to support checkout-in-place.


Instead, we get:

> LOCK nonexistentURL

  ...commits a 0-length file, locked...

> PUT 0-byte-file

  ...commits 0 more bytes to that 0-byte file... (leaving it locked)

> PUT real-file

  ...commits real content to the file, or 0 bytes again if the file
  has no content... (leaving it locked)


  ...unlocks the file.

Three commits, just to do "Save As ...". Purty icky. But, if that's
the grossest thing we'll ever have to face in developing Subversion,
we're doing juuuuuuuust fine.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 21 17:13:16 2005

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.