Subversion Prolem b/c moved files

Mickael Marchand marchand at
Wed May 11 11:57:09 BST 2005

David Faure a écrit :
> On Wednesday 11 May 2005 12:22, Michael Brade wrote:
>>On Wednesday 11 May 2005 10:42, Stephan Kulow wrote:
>>>Am Mittwoch 11 Mai 2005 10:16 schrieb Dirk Mueller:
>>>>All the KDE/ move breaks perfectly, so we could as well
>>>>have skipped the whole conversion process and just imported the latest
>>>>trunk into the SVN tree. Would have been as useful as it is now.
>>>What makes the KDE/ move different from any other svn move done after
>>>the conversion?
>>Not much. Just the little fact that the _whole_ KDE was moved, which means the 
>>history for all of KDE is not easily accessible anymore. BTW, in CVS there 
>>was no problem, because we copied the history to the new place as well.
>>Maybe svn could be fixed to allow for earlier revisions to be used at the new 
>>place, at least the diffs work there already. Maybe by adding a new switch to 
>>svn update or so.
> I think subversion-1.2 (almost out, it's in rc3 already) supports that; if I understood
> correctly the peg-revision concept.
yes, but not for svn update command apparently
it might be quite difficult to implement actually ...
I am not sure how the file could still be handled in the working copy
after such an update (if it existed ;)

(not to mention how users will scratch their heads trying to understand
the peg concept btw :)

for now, the simpliest way to actually get the file in, is probably "svn
sw -rthe_revision OLD_KDELIBS_URL/file.cpp file.cpp"
maybe we could add a script in kdesdk/scripts/ to make this easier...
("kdegetback -rrev file.cpp")


More information about the kde-core-devel mailing list