Erik Andersson wrote: > Will an upgrade to svn 1.5 still work with svnmerge.py? svnmerge.py uses its own svn properties which won't interfere with mergeinfo, you can convert at a later date or not.
S > > /E > > On Mon, Jan 12, 2009 at 11:58 AM, Erik Andersson <[email protected] > <mailto:[email protected]>> wrote: > > Hi > > We are currently using svnmerge.py and I'm very happy with it. > Some developers are though complaining about the blame function > beeing messed up since it's the CM that owns a lot of changes due > to the merges. I looked at upgrading to svn 1.5, but the merge > tracking seems to lack some functionality like blocking > changesets. Also, we do cyclic merges and svn 1.5 seems to make > that complicated. > > Is there anyone else who have decided not to use the merge > tracking in svn 1.5 and stick to using svnmerge.py? Please share > your experiences. > > If we upgrade to svn 1.5, will svnmerge.py work as fine as before? > I'm guessing I won't get the blame functionality properly though > if I still use svnmerge.py.. > > Cheers / Erik > > > ------------------------------------------------------------------------ > > _______________________________________________ > Svnmerge mailing list > [email protected] > http://www.orcaware.com/mailman/listinfo/svnmerge > _______________________________________________ Svnmerge mailing list [email protected] http://www.orcaware.com/mailman/listinfo/svnmerge
