Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

tortoise svn always merging 45 extra files

When we do our branching and merging with svn, we always have the same thing happen.

We get a latest copy of the trunk.

Create a branch and switch.

Make some small change on one file in the branch.

Merge branch back into trunk.

At this point, we'll have our one file that needs to be comittied, plus the same 45 extra files. This happens on every single branch and merge, and its always the same 45 extra files. I have no idea how to fix the problem, but its extremely annoying.

Has anyone ever seen this before?

UPDATE: When I do the commit, the files that I actually changed have their Text Status as modified and their property status as blank. The "45 files" are all Text Status normal, Property Status modified.

like image 484
Jonathan Beerhalter Avatar asked Apr 23 '09 19:04

Jonathan Beerhalter


People also ask

How do I undo a svn merge?

To revert (SVN lingo: reverse-merge) a range, simply swap the start and end revisions, e.g. -r 76100:76077 to revert -r 76077:76100 . To revert a single revision, use a negative revision ID, e.g. -c -76077 to revert r76077 (this is equivalent to -r 76077:76076 ).

What is a sync merge?

A sync merge is something completely different than a reintegration merge. The former is used to merge all changes made on the parent branch to the target branch (typically a feature branch), that have not already been merged. The latter is used to merge a (feature) branch back into the parent branch.

What is merge in TortoiseSVN?

TortoiseSVN helps you through this process by showing the merge conflict dialog. Figure 4.58. The Merge Conflict Dialog. It is likely that some of the changes will have merged smoothly, while other local changes conflict with changes already committed to the repository. All changes which can be merged are merged.


1 Answers

They're probably mergeinfo properties. With version 1.5 of SVN, it was quite aggressive with setting the mergeinfo property, and as you merge, those properties get updated - requiring a commit to them.

The answer is to delete the mergeinfo property from them. Also upgrade to version 1.6 which has better mergeinfo support (i.e. it writes less of these properties).

I should say that these file will have no visible changes if you look at the differences. Obviously, if their contents are changed, then what the changes are may give you a clue (e.g. is an automated tool writing extra comments, modifying the layout or adding lines to the top or bottom).


EDIT: See this blog post for more information on SVN merging issues, and fixes.

like image 64
gbjbaanb Avatar answered Sep 22 '22 03:09

gbjbaanb