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

Re: Partial fix for merge_tests.py 66 failure on mergeinfoless-copies branch

From: Karl Fogel <kfogel_at_red-bean.com>
Date: 2007-11-23 04:01:13 CET

"C. Michael Pilato" <cmpilato@collab.net> writes:
> So ... on the mergeinfoless-copies branch, 'svn copy' always results in
> mergeinfo being recorded, if only empty mergeinfo. In other cases besides
> WC->WC, so copy just go ahead and determine that, if none of the copy
> destination's parents have any mergeinfo, it should simply write no
> mergeinfo *at all*?

(I'm assuming 's/so/should/'.)

Do you mean "no mergeinfo at all besides what the copy source already
has", or do you really mean "no mergeinfo *at all*"?

The former makes sense to me (but, I may be too ignorant to understand
all the implications of what you're asking).

The destination's parents will still have the implicit mergeinfo that
comes from having history (and *their* parents having history, etc,
etc). And that implicit mergeinfo shouldn't apply to the copy... but
then it won't, because copies are treated specially in mergeinfo
inheritance rules anyway, right?

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 23 04:01:27 2007

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