I'm not subscribed, so please CC me in the answer
C. Michael Pilato wrote:
>I remember chatting about this feature in the past. It's certainly
>do-able. And seems useful, too. The complication that I see is that
>your destination file will have a fork in its ancestry, which means
>that answer questions like, "What did this line of history look like
>in <some revison prior to the join>?" kinda complicated. Does the
>answer include data from both tines of the fork (or all N of them,
>right -- this operation can commute)?
>
>Not that this is a new problem. We have the problem today, in trying
>to answer "What does this line of history look like in <some revision
>after a copy/branching operation>?"
>
>
Possible answer: let 'svn join <A> <B>' behave as 'cat <B> >> <A>'
That solves the problem about "from which revision comes this line".
This way a complete history for teh file can be generated. Let the user
do his reordering after that, as he can do to any single file. If you
want to know abot the history of the complete file (where it has been
trough several 'svn move') the history of file <A> will be used. Another
idea is a unversioned property svn:joined that can be used in some way.
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 17 06:33:41 2004