the post at [1] in about paragraph 5 has some useful insights --- I'm still working through it, but others may be able to apply more experience and tuscany history to these comments.
Kelvin [1] http://chrisoldwood.blogspot.com/2010/03/cleaning-up-svnmergeinfo-droppings.html On Thu, Jun 3, 2010 at 9:58 AM, Simon Laws <[email protected]> wrote: > On Thu, Jun 3, 2010 at 9:45 AM, ant elder <[email protected]> wrote: >> On Thu, Jun 3, 2010 at 9:25 AM, kelvin goodson <[email protected]> >> wrote: >>> When I do an svn:merge there are a host of files that I have not >>> modified that appear to need committing. I believe it is because they >>> have the svn:mergeinfo property set on them [1], To date I have >>> manually unselected these for commit, and reverted them after >>> committing my selected files. Can we remove this property everywhere >>> it occurs? >>> >>> Kelvin. >>> >>> [1] >>> http://stackoverflow.com/questions/2051267/why-would-svn-merge-of-a-branch-with-no-changes-causes-untouched-files-to-modify >>> >> >> Yes i find all the mergeinfo changes bothersome too so if it doesn't >> cause any side effects (and it doesn't sound like it will from the >> link you posted) then lets remove the property. >> >> ...ant >> > > > I see this too. I'm not really familar with the mergeinfo property. > From the link it seems to be recording information about what has > already been merged and from where. I would seem sensible to either > configure and use it consistently or remove it. > > My initial reaction yesterday on running a merge was to look at > committing the changes I was expecting and revert the numerous > properties changes. I think that this means that I'm in favor of > removing the properties. I'd just like to understand what we're > missing by not having them before we finally commit to removal. > > Regards > > Simon > > -- > Apache Tuscany committer: tuscany.apache.org > Co-author of a book about Tuscany and SCA: tuscanyinaction.com >
