

I think Ive found another 1.5 bug related to reintegrate.
I think this could be my problem, but I can't find anything indicating what if anything needs to be changed. From: Ruslan Sivak <> Date: Wed, 17:27:15 -0500.This Fedora 14 machine has been updated from an earlier version of Fedora, so our Subversion repository was most likely initially created with a pre-1.5 Subversion. The complete merge is used for the sync and reintegrate merges in the feature branch pattern described below. I've also checked the dates on apache svn modules (am I using apache with svn:// ?) The dates check out modules]$ ls -l *svn* Sync/Reintegrate/Symmetric merge: Synchronizes all missing changes from trunk (or a different branch) into this branch. When the branch is finished, he wants to merge it back (reintegrate) to its parent. These are both 1.6.17 -which should support the reintegrate feature. svn commit -message Integrate from trunk. A reintegrate merge is performed whenever a merge's direction differs from the direction of the previous merge. Working copy records moves as first-class operation Automatic reintegration merge Inherited properties Repository dictated configuration HTTP client.

Whether a sync or reintegrate merge is performed depends on prior merge history. In the examples that follow, were assuming that both your Subversion client and server are running Subversion 1.8 (or later). There is no reason to be surprised if the new 'complete merge' in Subversion 1.8 attempts to reintegrate the trunk into a branch. I've checked versions of svnserve and svn client. In Subversion terminology, the general act of replicating changes from one branch to another is called merging, and it is performed using various invocations of the svn merge subcommand. Svn: Retrieval of mergeinfo unsupported by 'svn://fedorabox/e2458/branches/ErrtsFeaturDev' I get the product_trunk]$ svn merge -reintegrate ^/product/branches/NewFeature What you are asking Subversion to do is: Calculate the changes necessary to get FROM the head revision of the trunk TO the head revision of the branch, and apply those changes to my working copy (of the. This is a more general case of the reintegrate method. You can now review the changes locally, resolve any conflicts, build and test. I'm trying to use the Subversion merge -reintegrate feature to merge a development branch back to the project trunk. This is known as a reintegrate or automatic merge. The reintegrate merge will merge all of the changes that are unique to your working branch and skip changes that are already in the trunk.
