Well, copies are normally recorded, so that'll still be there.
("copied from /some/where, rev RR").
Are you asking to record that a file was copied *to* elsewhere? Not
sure about doing that.
Cheers,
-g
On Wed, Sep 10, 2008 at 4:59 AM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Tue, Sep 09, 2008 at 12:26:02PM -0400, Karl Fogel wrote:
>> "Greg Stein" <gstein_at_gmail.com> writes:
>> >> Also, for the 'moved' and 'copied' enums, would they refer to the source
>> >> or dest of the operation?
>> >
>> > This is the status of the destination, just like our current interface.
>> >
>> > But your point is good: what about the source of a move. In order for
>> > this API to properly represent a move, the source is not "deleted",
>> > but "moved away". I'll update the enum to clarify that situation.
>>
>> Sounds good.
>
> Yes, please track moves both ways!
> And copies, while at it.
>
> This would help a *lot* with tree conflicts.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: dev-help_at_subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-10 15:40:03 CEST