Client 1.5 will only touch the working copies and automatically upgrade (1.4.3) to 1.5. And svnmerge.py still continues to work effectively with the 1.5 client. Are there any specific use cases out there for which svnmerge.py outperforms the 1.5 release? To use any of the merge tracking features of 1.5, your repository would also have to be promoted to 1.5
On Tue, Jul 1, 2008 at 9:49 AM, Rekha Gupta <[EMAIL PROTECTED]> wrote: > According to build management group who are keepers of SVN in my > esteemed organization; its all right to go ahead and upgrade to client > 1.5. Not sure how many new features would work without server upgrade > but client should be backward compatible. > > Thanks > Rekha > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Paul Walmsley > Sent: Tuesday, July 01, 2008 9:35 AM > To: [email protected] > Subject: [Svnmerge] Compatibility of svnmerge with 1.5 clients but > 1.4server? > > Hi, > > Does anyone know about the compatibility of using svnmerge with 1.5 > clients but a 1.4 server? We don't intend to upgrade our server yet but > > people may update their clients to 1.5 to get some of the new features. > > Will svnmerge work correctly in this case? I seem to recall trying it > with a beta of a 1.5 client on windows and not having much luck, though > that could have been for a number of reasons. > > thanks > Paul Walmsley > _______________________________________________ > Svnmerge mailing list > [email protected] > http://www.orcaware.com/mailman/listinfo/svnmerge > > > _______________________________________________ > Svnmerge mailing list > [email protected] > http://www.orcaware.com/mailman/listinfo/svnmerge > -- Best Regards, Rohan Joseph _______________________________________________ Svnmerge mailing list [email protected] http://www.orcaware.com/mailman/listinfo/svnmerge
