• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Maximum risk when deleting all svn:mergeinfo properties in Subversion

 
best scout
Posts: 1294
Scala IntelliJ IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello rangers,

I have some merge problems in Subversion. There are currently a few branches which are directly branched off of the trunk. Now there is a problem with the SVN metadata (most probably the svn:mergeinfo properties) when I try to merge new changes from the trunk into one of the branches. Obviously SVN doesn't recognize some changes (which are really there) because it thinks the corresponding revisions are already merged into the branch.

The idea to solve this problem the easiest way seems to be to delete all svn:mergeinfo properties. Can anybody tell me what could be the maximum impact when deleting all these properties in the trunk and all open branches? I suppose it could only be a little bit harder to reintegrate the open branches. Are there any other disadvantages which could result from a complete cleanup of mergeinfos?

Marco
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic