I don't like when threads are combined unless they are actually about the same problem. Example: Poster 1 posts "Is Maritz down?" and thirty minutes later Poster 2 posts "Maritz down for maintenance tonight." Maybe one posted in MS discussion and the other posted in MS Company discussion. It makes sense to combine those since they are actually about the same outage.
But I wouldn't want to see them combined with another thread by the same name from two years ago.
And if one poster posts about a problem with an Intellishop editor, I don't want to see that combined with someone else's rant about an IS editor. They are two different problems. Why discuss them both in the same thread?
I think I would rather see multiple threads where one has been locked instead of combining them (in my Maritz example) with a link to the post that is being allowed to survive. It gets very confusing to know who is replying to what when two threads of more than a few posts each have been combined.
I think maybe we should consider that threads can be about policy (when does Maritz pay), technical (how do I submit an invoice), procedural advice (should I do the drive thru or the eat in first), anecdotal (you won't believe what the clerk said to me!), warnings (anyone else not get paid by Confero?), new shop (about to do my first xxxx shop; any advice?), curiosity (how many hours do you spend hunting for jobs), informational (what records should I keep for my taxes?), shop procedures (understanding the requirements). Just because the word "Sentry" appears in several threads doesn't mean they are the same kind of thread. Policy, Technical, Informational, Procedural -- maybe multiples in those areas could be combined (I mean Policy with Policy, Technical with Technical). But Advice, Anecdotes, Warnings, New Shops, Curiosity (which may belong in the General Chat area anyway) probably are situation-specific and should never be combined.
I would suggest that when in doubt, don't combine. And don't combine if there are more than 5 responses in each thread because the conversation will get mangled in the process. Lock one instead.
Time to build a bigger bridge.