RE: svn commit: r966770 - in /subversion/trunk/subversion/libsvn_wc: copy.c log.c log.h merge.c workqueue.c workqueue.h

[Bert Huijben <be...@qqmail.nl>]

> -----Original Message-----
> From: Daniel Shahaf [mailto:d.s@daniel.shahaf.name]
> Sent: donderdag 22 juli 2010 20:58
> To: dev@subversion.apache.org
> Cc: commits@subversion.apache.org
> Subject: Re: svn commit: r966770 - in
> /subversion/trunk/subversion/libsvn_wc: copy.c log.c log.h merge.c
> workqueue.c workqueue.h
> 
> rhuijben@apache.org wrote on Thu, Jul 22, 2010 at 17:44:41 -0000:
> > Author: rhuijben
> > Date: Thu Jul 22 17:44:41 2010
> > New Revision: 966770
> >
> > URL: http://svn.apache.org/viewvc?rev=966770&view=rev
> > Log:
> > Replace the file-move loggy operation with a file-move wq operation.
> >
> > This to move away from loggy and to fix some cross directory
> > issues on using adm_abspath, when running with a single-db.
> 
> So the work queue (which, IIUC, replaces loggy) uses absolute paths?
> 
> How would this affect
> 
> 	% svn break-the-wc /path/to/wc
> 	svn: an error occured; run 'svn cleanup'
> 	% /bin/mv     /path/to/wc /elsewhere
> 	% svn cleanup /elsewhere

Currently it uses absolute paths, so yes you have this issue (and you had
the same issue for at least half a year), because we can't really use the
working copy relative infrastructure yet. (This is too much dependent on
single-db).

Before 1.7 these paths will be we working copy root relative. See the note I
added with this commit

	Bert
> 
> ?
> 
> 
> Daniel
> (if it's documented, I'll appreciate a pointer to the docs, thanks.)