Several times, there are questions that are not exact duplicates, but happen to have very similar answers. What is the correct protocol? Is it appropriate to cut-and-paste an answer and link to the original, so that if it doesn't get merged, it sticks, and if it does, it's clear how to clean it up? This just came up twice in 5 minutes for me, and I want to make sure I'm not "gaming anything" by posting an answer twice, today in particular to "my django thing isn't working" to which I respond with a checklist -- the problem is different, but the answer is similar. Cases in point for me today are this and this. Still absorbin' the culture here...
If the questions are completely distinct and not duplicates then the correct response would be to answer the question on the question page. You should also link to your previous answer and copy out the relevant information.
A similar issue was approached here:
I solved it by using XYZ
"When confronted with QRS, you should really use the < InsertPatternHere > model. It solves the issue by using < magic >. I have helpful and explanatory links here, here and here. I've also finished my answer with a < poignant yet witty rejoinder || cautionary note >.
In your case, there are relevant differences of Foo and Bar. However, the solution will still work because of < some brilliant reason >.
In this way, they are still separate answers. This is important because the OP may later reveal that one or the other question is actually not what you originally thought it was. Additionally, it helps users who found there way here from a Bing search because the answer they want will be right on the page in front of them, rather than requiring an additional blind-link-click to find some other page that might have the answer.