You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Scott Lamb <sl...@slamb.org> on 2002/08/22 07:47:56 UTC
Re: [Issue 876] Changed - svn revert of svn move
issues@subversion.tigris.org wrote:
> http://subversion.tigris.org/issues/show_bug.cgi?id=876
>
> + ------- Additional Comments From blair@tigris.org 2002-08-21 18:16 PDT -------
> + Ideally, you could say
> +
> + svn revert hot-backup-db.py
> +
> + and it would do the following:
> +
> + 1) Revert hot-backup.py.
> + 2) Revert hot-backup-db.py.
> + 3) Delete hot-backup-db.py.
Most intuitive IMHO is just executing the reverse before committing the
change. I.e., "svn mv oldfile newfile" is reverted by "svn mv newfile
oldfile". Other modifications (to the file's contents or properties) are
not reverted by that command.
--
Scott Lamb
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 876] Changed - svn revert of svn move
Posted by Scott Lamb <sl...@slamb.org>.
Branko Čibej wrote:
> Scott Lamb wrote:
>
>> issues@subversion.tigris.org wrote:
>>
>>> http://subversion.tigris.org/issues/show_bug.cgi?id=876
>>>
>>> + ------- Additional Comments From blair@tigris.org 2002-08-21 18:16
>>> PDT -------
>>> + Ideally, you could say
>>> + + svn revert hot-backup-db.py
>>> + + and it would do the following:
>>> + + 1) Revert hot-backup.py.
>>> + 2) Revert hot-backup-db.py.
>>> + 3) Delete hot-backup-db.py.
>>
>> Most intuitive IMHO is just executing the reverse before committing
>> the change. I.e., "svn mv oldfile newfile" is reverted by "svn mv
>> newfile oldfile". Other modifications (to the file's contents or
>> properties) are not reverted by that command.
>
> Except that that doesn't work, because our working copy can't handle it.
Right. By "is reverted by", I meant "should be reverted by". Sorry if I
caused confusion.
--
Scott Lamb
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 876] Changed - svn revert of svn move
Posted by Branko Čibej <br...@xbc.nu>.
Scott Lamb wrote:
> issues@subversion.tigris.org wrote:
>
>> http://subversion.tigris.org/issues/show_bug.cgi?id=876
>>
>> + ------- Additional Comments From blair@tigris.org 2002-08-21 18:16
>> PDT -------
>> + Ideally, you could say
>> + + svn revert hot-backup-db.py
>> + + and it would do the following:
>> + + 1) Revert hot-backup.py.
>> + 2) Revert hot-backup-db.py.
>> + 3) Delete hot-backup-db.py.
>
>
> Most intuitive IMHO is just executing the reverse before committing
> the change. I.e., "svn mv oldfile newfile" is reverted by "svn mv
> newfile oldfile". Other modifications (to the file's contents or
> properties) are not reverted by that command.
Except that that doesn't work, because our working copy can't handle it.
Anyway, we need better tracking of renames and moves. We shouldn't be
creating new nodes in the repository, and I have a ToDo to open a new
issue about that. I know this came up before, and I was against
explicitly tracking renames then; but that was before we had a coherent
schema, in which a node id really means something. It's time to
reconsider now.
--
Brane Čibej <br...@xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org