Raman Gupta wrote: > A refactorization of the code in revision 18696 that checks for > reflected revisions broke it for a corner case. The current code > may incorrectly consider the first revision to be reflected even > when it is not. This can occur if the first revision included a > change to the merge property, but one that did not change the > merged revision list for the source branch. > > See my patch below. Since old_revs is not initialized in the loop > that checks the merge_metadata_changed revs, the first rev to be > checked is ALWAYS considered reflected.
Has anyone remembered about this outstanding patch submission? Giovanni or Blair? http://www.orcaware.com/pipermail/svnmerge/2006-May/000591.html Cheers, Raman _______________________________________________ Svnmerge mailing list [email protected] http://www.orcaware.com/mailman/listinfo/svnmerge
