On 10/5/06, Giulio Troccoli <Giulio.Troccoli@uk.linedata.com> wrote:
> I am using Subversion 1.3.0 (r17949) on an AIX system and I have noticed this strange behaviour. I'd like to know if anybody else has experienced it and/or I am doing something wrong. If not I will post an issue.
>
> I have delete an whole directory (dip/dscomms) and it has been scheduled correctly
>
> agrippina[ksh]%src>svn status -q
> D dip/dscomms/dsCommsLogin.c
> D dip/dscomms/dsCommsSystemParameters.c
> D dip/dscomms/dsCommsConnect.c
> D dip/dscomms/dsCommsDisconnect.c
> D dip/dscomms/dsCommsSend.c
> D dip/dscomms/dsCommsInitialise.c
> D dip/dscomms/makefile.svn
> D dip/dscomms/dsCommsWaitForUpdate.c
> D dip/dscomms/dscomms_local.h
> D dip/dscomms/dsCommsSimulator.c
> D dip/dscomms/dsCommsGlobals.c
> D dip/dscomms/dsCommsChooseDLIVE.c
> D dip/dscomms/dsCommsInvokeAPI.c
>
> Then I have changed my mind and revert it
>
> agrippina[ksh]%src>svn revert dip/dscomms
> Reverted 'dip/dscomms'
>
> Here the first problem. The files are NOT restored from the BASE and the dip/dscomms directory is empty
That's correct: you didn't ask svn to: the revert command is by
default *not* recursive. You probably wanted 'svn revert -R
dip/dscomms'.
> agrippina[ksh]%src>ls dip/dscomms
> agrippina[ksh]%src>
>
> And the files are STILL scheduled for deletion
As expected. I hope the above suggestion helps.
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 5 17:33:02 2006