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

Re: ra_dav and mod_dav_svn target problem

From: <cmpilato_at_collab.net>
Date: 2003-08-05 19:57:48 CEST

Chia-liang Kao <clkao@clkao.org> writes:

> On Tue, Aug 05, 2003 at 11:57:18AM -0500, cmpilato@collab.net wrote:
> > Targets have to be single path components. This should be:
> >
> > my ($anchor, $target) = ('http://svn.collab.net/repos/svn/trunk/subversion',
> > 'mod_authz_svn');
>
> Did you see my intention to use path of multiple components
> in the original message?

Can't say that I did.

> a specific example: /trunk/subversion/bindings/swig @ 1038, python
> and python/svn are added. how do we do a diff/update for python/svn
> of 1308 from 1307? shouldn't bindings be the anchor and python/svn
> be the target?

If you want to update "/trunk/subversion/bindings/swig" from revision
1307 to revision 1308, you anchor on "/trunk/subversion/bindings", and
"swig" is your target. The update editor will then be driven in such
a way that you can take the paths from editor functions (which are
relative to the root of the edit drive), and slap them together like
this:

   anchor [+ edit_path] = working_copy_path

The rules of anchors and targets are pretty simple:

   1. anchor + target = the thing you want to work on.
   2. target may be NULL or a single path component.
   3. anchor must be a directory.

And there's an additional recommendation:

   4. if there is a possibility that the thing you want to work on
      might be deleted, you probably want to anchor on its parent so
      that the editor driver can call editor->delete_entry() on the
      thing you want to work on.
      

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 5 19:59:57 2003

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.