On 7/26/06, Tom Vaughan <tom@creativedigitalsys.com> wrote:
> 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.
Because it matters to the repository what's between these revision
numbers: commits are related. Why is it that you want your number back
to N? Because then you can start committing from your working copy
again? Or just 'for optical reasons'?
You can't commit from that working copy anymore, supposing that you
have files which were modified in the region that just got deleted. If
such modifications are no longer in the repository, your working copy
and repository just got out of sync...
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 26 21:52:19 2006