kfogel@collab.net wrote:
> > So I think this feature can be reasonably implemented by always
> > making copies from the most recent revision of the copied file in
> > the target repo. Anything fancier is then declared beyond the scope
> > of this feature.
> >
> > What do other people think? How hard is this to implement?
>
> I'm rather confused by the parameters of this discussion.
>
> What does "most recent revision" of anything have to do with it? The
> merge command names specific revisions, so it's not as if finding the
> relevant changes in the source repos is the difficult part...
We're talking specifically about using 'svn merge' to merge in
changes from a different repository, something that's not currently
supported.
I won't repeat the whole thread (if the web site search function
wasn't broken I'd give you the link), but it basically boils down
to this question: when merging in a revision that, in the source
repository, created a new file "file2" via a copy-with-history of
revision XXX of "file1", what revision YYY of "file1" in the
(different) target repository should the new "file2" in the target
repository be a copy of?
-Archie
__________________________________________________________________________
Archie Cobbs * CTO, Awarix * http://www.awarix.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 18 18:45:18 2004