[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Anyone wanna finish off the correct-copy-mergeinfo branch?

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2007-12-13 14:32:46 CET

I'm gonna be offline for the next several days. I've got the logic on the
correct-copy-mergeinfo branch ready as far as I can tell. There are just a
few remaining merge-tests whose expectations haven't been reviewed
(basically tests 63 and higher). If someone gets some free time, and
understands what these tests should now expect, and wants to finish that
branch and merge it to trunk while I'm away, that'd be swell.

I might as well tell you what the test should expect. It's pretty
straightforward. Today's trunk, for any type of copy (and thereby also
move) operation, will create some sort of svn:mergeinfo property on the
target of the copy -- either with a value that is identical to the explicit
or inherited mergeinfo of the copy source, or failing that, an empty property.

On my branch, this changes in that for WC->REPOS, REPOS->WC, and
REPOS->REPOS copies, the code will never manufacture empty mergeinfo on the
copy target. (Though, I guess it can still write empty mergeinfo if the
copy source happened to have some explicitly empty mergeinfo on it.) WC->WC
copies, though, behave as they do on today's trunk with the exception that
the repository is never consulted when asking about the copy source's mergeinfo.

Poke Paul Burba or David Glasser with further questions, if you care -- I
think they understand this well.

C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 13 14:53:15 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.