Jeff S wrote:
> Hi Ruslan,
>
> Thank you for the prompt response!
>
> The binaries are long gone unfortunately. I did have
> another idea that might work?
>
> The last person who commited, will have all the
> latest code on their machine. So we can update
> the repository by having them:
>
> 1. Make another directory "c:\tmp\ccr" on your machine
> that we will call your update-copy.
> 2. Using Tortoise check out another working copy into
> that new folder you created above.
> 3. Copy over the files that were changed from the
> working copy into their matching folder locations
> in the update-copy.
> 4. Do another commit.
>
>
> Only six files were changed. So we would lose some
> revision levels but the repo would be updated. Does
> it sound like a good solution to you?
>
> Thanks, Jeff
>
Jeff,
From your earlier note, it appears that you are only a couple of
revisions back. Which probably means that you backed up your old
repository while others were still committing to it. If you are
confident that you have a user with those latest changes, you can commit
the 6 files that were changed as 6 separate commits to bring the
revision numbers up. If you need more, it could be as simple as adding
a line feed to a file and then removing that line feed. Anything to
cause a difference to bring the revision number up.
Then the others should be able to commit as well.
Regards,
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 6 22:55:30 2006