RE: [PATCH] Issue 898 atomic rename, implement svn_fs_rename

I took care of the cross-history issue, yes. However,
svn_fs_node_revisions_changed's current API can't handle returning a
rename that has a source and target path atm. (i.e. folding together the
mv-target, and the delete change entries into something comprehendable.)

Bill

---
Do you want a dangerous fugitive staying in your flat?
No.
Well, don't upset him and he'll be a nice fugitive staying in your flat.
 
 -----Original Message-----
 From: cmpilato@collab.net [mailto:cmpilato@collab.net] 
 Sent: Thursday, January 23, 2003 9:32 PM
 To: Bill Tutt
 Cc: 'Branko Cibej'; Philip Martin; dev@subversion.tigris.org
 Subject: Re: [PATCH] Issue 898 atomic rename, implement svn_fs_rename
 
 
 Bill Tutt rassilon@lyra.org writes:
 
  It'll probably be a day or so before I commit this stuff to 
 the 1003 
  branch, so if anyboy has any other issues they can think of, or a 
  better idea please speak up. :) Note: I don't plan on 
 solving the WC, 
  svn log output,  or svn_fs_node_revisions_changed API 
 issues with this 
  particular set of changes. Just going to ensure that the core 
  tree.c:open_path code path can handle the rename problem.
 
 I thought you'd already taken care of 
 svn_fs_node_revisions_changed()'s 
 problems!?
 
 ---------------------------------------------------------------------
 To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
 For additional commands, e-mail: dev-help@subversion.tigris.org
 
 
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org