Paul,
Are you implying that, for a move to carry history, the delete and add
operations have to be committed at the same time? If a "move" is just a
delete+add, with the add getting extra metadata, why can't you commit
the delete and the add in separate revisions?
I'm guessing what you meant is that one can *infer* a move as
distinguished from a copy if there was a deletion of the original files
in the same revision.
Garret
Paul Koning wrote:
>>>>>> "Garret" == Garret Wilson <garret_at_globalmentor.com> writes:
>>>>>>
>
> Garret> A client of mine finally switched from CVS to Subversion
> Garret> 1.5. I had been extolling the virtues of Subversion,
> Garret> including history.
>
> Garret> Starting with freshly converted repository, a team member
> Garret> moved /repo/trunk/old to /repo/trunk/new .
>
> Garret> I pull up the Subclipse 1.4 (supporting Subversion 1.5)
> Garret> inside Eclipse 3.4 and look at the log of /repo/trunk/new . I
> Garret> only see the addition of /repo/trunk/new . I don't see any
> Garret> previous history of /repo/trunk/old .
>
> Garret> What single, simple command can I make to verify
> Garret> unambiguously whether /repo/trunk/new has history connecting
> Garret> it to /repo/trunk/old ?
>
> "svn log -v" will show "(from <pathname>:<revnum)" on the new pathname
> if a copy or move was done.
>
> To distinguish a copy from a move, see if the same rev also contains a
> delete operation on the old path (the one mentioned in "from"). If
> yes then it was a move.
>
> paul
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-02 23:16:12 CEST