Rather than mess with the repository, why not just undo the commit? “Merge –r 64:62” will do that (in a working directory) after which you can commit the result.
It’s all in the book. It’s easy and fast, and it doesn’t require access to the repository guts, only commit rights.
paul
From: Richard.Herwig_at_wellsfargo.com [mailto:Richard.Herwig_at_wellsfargo.com]
Sent: Tuesday, September 30, 2008 1:55 PM
To: users_at_subversion.tigris.org
Subject: Repository Dump/Delete/Load Log History Issue (maybe)
So... let's just say I accidentally deleted a couple of files (read: directories >:-( from my repository AND the (foolishly) committed the delete. DOH!
No problem, simply dump the previous versions of the repository (not including the delete), delete it, and re-create it using the dump file.
>svnadmin dump /my/repository -r1:62 > dumpfile.txt
>mv /my/repository /my/repository_bakup
>svnadmin create /my/repository
>svnadmin load /my/repository < dumpfile.txt
The dumpfile.txt looks OK (last line = "------- Committed revision 62 >>>")
Revisions 63 and 64 were the commits that I wanted to back out.
Looking at the history log, everything looks good.
However, upon my next 2 commits the history log file shows the text from the old 63 and 64 (commit 65 no shows the proper text).
Looks like even though I dumped revisions 1 through 62, the dumped history file still had 64 entries in it.
Richard Herwig
Received on 2008-10-01 17:56:08 CEST