Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
> We use double j merges often here; I guess > it depends on your workflow. Developers > mostly commit to the HEAD; upcoming > releases have their own branch. QA > doesn't want all changes, just some of those changes. But you can do all of that with a single j merge and a change set number - that's why they are there. In my understanding a double j merge just means you are telling cvsnt NOT to record the merge... I don't know of a reason why a double j merge couldn't record the mergepoint, I don't think anyone ever thought anyone used double j merges anymore (there is certainly no need to). Regards, Arthur