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

Re: 'svn up -r0' doesn't.

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Mon, 4 Jul 2011 13:35:39 +0300

Philip Martin wrote on Mon, Jul 04, 2011 at 10:18:49 +0100:
> Philip Martin <philip.martin_at_wandisco.com> writes:
>
> > I really follow what you are doing, what you expect to happen or what
> > did happen. Can you produce a simple recipe?
>
> That should be "I didn't really follow". When I run 'svn up -r0 m' the
> target m doesn't appear to exist (because the earlier update failed?)
> and I get no conflict, just "At revision 0.".

What I do:

svn up -r 0 $SUBDIR

What happens:

after the update, the whole $SUBDIR/** hierarchy is present

What I expect to happen:

after the update, as I understand your earlier emails,
[ `find $SUBDIR | wc -l` -le 2 ]

What I did: in the email I wrote 'svn up -r 0 m' (rather than the actual
name of that directory) because the infra repository is not public. On
my shell session, m/f/h/e/ really was m*/f*/h*/e*/.
Received on 2011-07-04 12:36:40 CEST

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