Subversion Copy (copied_from)

Hello again, Info: Sun Solaris SPARC 9 subversion-1.4.2 using standalone I'm not entirely sure if this is a bug but it seems to me that it might be. [repos]/dir1/dir2/file.txt where dir1 is copied or moved to: /dirX and the resulting subdirectories are also copied/moved so that the new access would be: [repos]/dirX/dir2/file.txt In the repository dirX will return the fact that it was copied (even if it was moved--that's possibly another bug) but everything below (dir2 and file.txt) will not report the fact that they were copied (or moved) from their original location under [repos]/dir1. This is according to fs.copied_from API (as seen through ViewVC and even the TortoiseSVN client show log feature). Please note that files DO maintain the full history and that revisions prior to the revision where they were copied/moved indicate the original path, but the revision that they were actually copied/moved in does not contain the extra info about where it came from at that point (but the main directory does). First of all, is this intended or is this a bug? I cannot see a reason that the files underneath the primary directory being copied/moved would gain a new revision number but not have the copied_from field present--especially given the fact that the primary directory that was the argument for the copy/move did receive this field. The good news is that this isn't really a show stopper--showing the full log reveals the obviousness that the directory or files beneath the primary were in fact copied from another location originally (by noting that @rev-1 has a path field that differs from the current path), but I do believe it to be a bug that should be fixed someday unless there's a specific reason for it. -Q ____________________________________________________________________________________ Looking for earth-friendly autos? Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/
Received on Tue Jan 23 19:17:05 2007