[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: how to check-in to a deleted repository?

From: Christopher Ness <chris_at_nesser.org>
Date: 2005-09-27 01:54:52 CEST

On Mon, 2005-09-26 at 16:39 -0700, THOMAS DAVID VAUGHAN wrote:
> i have a repository that i deleted. for example, let's say i did:
> svn co https://server/repos/foo/tag/1 foo-1
> svn rm foo-1
> but then, later, i also did:
> svn co -r 263 https://server/repos/foo/tag/1 foo-1
> where 263 is the revision number just prior to the delete. and now i've
> found that i need to update a file. but i can't because i've deleted

Do a reverse merge to bring back the deleted data on the server using
the URL. Then update your working copy to the revision the reverse
merge creates, make your changes and commit.

        svn merge -r264:263 https://server/repos/foo/tag/1
        ## Now your repository is at the same state as 263
        svn up foo-1
        ## Brings your repository to HEAD which should likely be 256
        ## so you can make your changes and commit

> this repository (the idea being that it would just be deleted from the
> trunk, but still in the repository for historical retrieval). and ci
> doesn't take a "-r 263". i would expect the "-r 263" to be sticky
> anyway. so how do i do this?

Then you can delete the path (not the repository, but that's a
terminology nit) from the repository again.

You do not control revision numbers, they control you. :)

> also, is there anyway to set FOO_1 to revision number 263?

I don't understand. Do you mean like a macro to replace instances of
`FOO_1' in a file with the revision number of that file?

If so, see the FAQ:


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 27 01:56:23 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.