Stefan:
> I'm regularly using the svn mergeinfo normalizer myself. It should suit your 
> requirements quite well, but you'd be aware that it hasn't been tested 
> thoroughly by a lot of people, since it's a new tool in the not yet released 
> 1.10 development branch.
> 
I will test out this tool.  However, we are running on CentOS 6.9 and I may not 
be able to get all its dependencies installed.
> To get some basic documentation about what the tool does, best start with the 
> integrated help (svn-mergeinfo-normalizer help).
> In your case all you might actually need is to run "svn-mergeinfo-normalizer 
> normalize --remove-obsoletes" followed by committing the changes. Carefully 
> verify the changes before committing them. As said: The tool hasn't gotten 
> much test coverage by a broader audience yet.
> 
Yes, I am very careful about inspecting all changes before committing a change.
> If you wanna give it a quick try and are running on Windows, there are 
> prebuilt binaries available for MaxSVN (disclaimer: that's a development 
> binary distribution of SVN I'm 
> maintaining):http://www.luke1410.de/typo3/index.php?id=97 
> <http://www.luke1410.de/typo3/index.php?id=97>. Download MaxSVN 
> trunk-dev-r1771118-1 and run svn-mergeinfo-normalizer contained in the 
> package. I'm not aware of other prebuilt sources of the current SVN 
> development branch (otherwise I'd have listed them here as other examples).
> 
If I can’t get the tool running on our Linux systems, I will definitely check 
this out.
> On a more general note on your questions:
> Is it safe to do that (i.e. remove the entries for obsolete/removed branches)?
> 
> Kind of. If your working process means that you are not going to reinstate 
> the removed branch in a future revision again to merge remaining revision 
> from it to some other branch, I'd personally consider it a safe habit to drop 
> the then obsolete mergeinfos. If your work process differs, you should not 
> remove it though IMO, since then you might cause conflicts on merges and also 
> lose the information about what was merged of the other branch (if it later 
> is reinstated).
> 
We don’t plan to ever reuse those branches again, and in fact most of them will 
be deleted.

Thanks again for all your comments.  I’ll report back with my findings when I 
get a chance to run this tool sometime later this week.

Alfred

Reply via email to