Ruslan Sivak wrote:
> Ryan Schmidt wrote:
>> On Apr 10, 2008, at 6:46 AM, Steven Bakke wrote:
>>> If 'svn delete' were able to handle deleting items that are
>>> considered missing by svn status, that would be really useful.
>>
>> svn is able to handle that...
>>
>>
>> $ svnadmin create repo
>> $ REPO=file://`pwd`/repo
>> $ svn co $REPO wc
>> Checked out revision 0.
>> $ cd wc
>> $ touch foo
>> $ svn add foo
>> A foo
>> $ svn ci -m ""
>> Adding foo
>> Transmitting file data .
>> Committed revision 1.
>> $ rm foo
>> $ svn st
>> ! foo
>> $ svn rm foo
>> D foo
>> $ svn st
>> D foo
>> $ svn ci -m ""
>> Deleting foo
>>
>> Committed revision 2.
>> $
>>
>>
> I think he meant something like this should work, but currently
> doesn't: This is a sample script, with some command switches made up
> to illustrate how I think it should work.
> $ svnadmin create repo
> $ REPO=file://`pwd`/repo
> $ svn co $REPO wc
> Checked out revision 0.
> $ cd wc
> $ touch foo
> $ touch foo2
> $ touch foo3
> $ svn add --force .
> A foo
> A foo2
> A foo3
> $ svn ci -m ""
> Adding foo
> Adding foo2
> Adding foo3
> Transmitting file data .
> Committed revision 1.
> $ rm foo
> $ rm foo2
> $ rm foo3
> $ svn st
> ! foo
> ! foo2
> ! foo3
> $ svn ci --force -m ""
> Deleting foo
> Deleting foo2
> Deleting foo3
> Committed revision 2.
> $
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
I thnk that last one needs to be more like
svn ci . --force -m ""
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-04-17 21:06:45 CEST