[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

What's the best practice of such merge situation?

From: albert kong <albertkong1984_at_163.com>
Date: Thu, 22 Jul 2010 03:08:40 -0700 (PDT)

I have a MFC dialog project in the trunk and a branch, the branch implement
some features to fulfill a client's unique request.
In the branch I edit so many in resource design. Now I add a paramount
function to the branch, both edit the dialog resource and code. I need to
integrate this change to trunk also, I found merge the resource file now is
a disaster. I had to repeate the UI change again manually.
According your experience, what's the best design or practice in such
situation?
Hope I express it clearly!

-- 
View this message in context: http://old.nabble.com/What%27s-the-best-practice-of-such-merge-situation--tp29235194p29235194.html
Sent from the tortoisesvn - users mailing list archive at Nabble.com.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2636857
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-07-22 12:08:56 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.