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

Re: use svnadmin to set revision number?

From: Tom Vaughan <tom_at_creativedigitalsys.com>
Date: 2006-07-26 19:48:35 CEST

On Wed, 2006-07-26 at 18:36 +0200, Ryan Schmidt wrote:
> On Jul 26, 2006, at 18:08, Tom Vaughan wrote:
>
> > I don't think the state of what I have checked out matters. As I'd
> > have
> > to strip out everything ".svn", and then copy just the "content" over
> > into a new checkout from the old repository. So that's something like:
> >
> > mv project1 project1.latest
> > svn co https://oldserver/project1 project1
> > cd project.latest
> > find . -type f | grep -v .svn | \
> > xargs -I '{}' cp -a '{}' ../project1/'{}'
> > cd ../project1
> > svn ci project1
> >
> > No?
>
> Yes, you'd have to do something like that -- move the old working
> copy out of the way, make a new one, and manually move over the
> changes. And the point is everyone would have to do this somehow.
> Nobody would be able to continue using their old working copies.

How is that? This goes back to my original question of bumping up the
revision number in the repository so it is at least n + 1, where n is
the biggest repository number any one could have, and I know what that
number is. It's the number I have checked out.

-Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 26 19:50:43 2006

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