On 8/18/2010 8:07 AM, Steven Koch wrote:
Hi,
I need update the servers, and continue send changes to the point
3243! but actual content of SVN server are different (now r3251 is
considered new files, same that they are equals files)
If you deleted the trunk and then committed new copies of the files to
it, they are new files to svn. Even if the content is the same there is
no way to see the ancestry.
My revision in local copy is 3243 but in SVN server 3251
I think that solution is rollback the same revision of the servers
(stagging and production) and later apply the changes in content and
update servers(stagging and production)!
But I can rollback in my local copy to r3243 but not can commit this
revision or point!
If you want to put what was in 3243 back to the head of the trunk, you
should be able to delete the trunk again, then copy it in the repository
using peg notation for the source URL to indicate the revision before
the deletion. This should put it back at the HEAD with a history that
goes 'around' the deletions. Then you'd have to repeat any changes that
you wanted to keep that were made after the peg revision you copied.
I'd recommend trying this in a test repository first to see if you get
the effect you want.
--
Les Mikesell
lesmikes...@gmail.com
