Comments on: Discard candidate merge changesets http://intovsts.net/2012/08/30/discard-candidate-merge-changesets/ blogging about Application Lifecycle Management with Team Foundation Server Fri, 17 May 2013 10:11:42 +0000 hourly 1 http://wordpress.com/ By: pietergheysens http://intovsts.net/2012/08/30/discard-candidate-merge-changesets/#comment-1844 Sat, 20 Oct 2012 21:00:29 +0000 https://intovsts.wordpress.com/?p=705#comment-1844 a new changeset will indeed be created, but it will not pop up as a candidate changeset for merging in the other direction if no additional changes have been applied in the same changeset!

]]> By: Oran http://intovsts.net/2012/08/30/discard-candidate-merge-changesets/#comment-1830 Fri, 19 Oct 2012 08:59:39 +0000 https://intovsts.wordpress.com/?p=705#comment-1830 Thanks for the post, it’s really helpful but I have one question.

Because it’s still required to check in the change on the “target” branch (even though there are in fact no changes) TFS creates a new changeset on the “target” branch which then appears as a merge candidate for a reverse merge.

Seems to me like it’s only moving the problem from one place to another. Am I missing something?

Thanks

Oran

]]>