Skip to main content
Reworded slightly so that the old information is past-tense. Makes it a bit easier to follow
Source Link
Robotnik
  • 4.4k
  • 1
  • 21
  • 34

Impossible at the momentPreviously this was impossible, as one of the merged questions (the source) iswas literally destroyed -- it doesn't exist any more.

  A merge record is recorded in the history of the target question, but it's not in any kind of reasonably queryable format.

It sounds to me like you're arguing for keeping the duplicates, closing as duplicate, and just shuffling the answers around, which is a different request.

Merge is for PERFECT duplicates.

edit: weWe now handle question merging in a much more sane way -- both questions are retained, one is a stub, and all answers are migrated into the merged question. If the stub is deleted, we 301 redirect to the merge target.

https://blog.stackoverflow.com/2010/06/improved-question-merging/

(nothing Nothing can be done about old merges, sadly, due to our poor choice to destroy the other question in the merge)

Impossible at the moment, as one of the merged questions (the source) is literally destroyed -- it doesn't exist any more.

  A merge record is recorded in the history of the target question, but it's not in any kind of reasonably queryable format.

It sounds to me like you're arguing for keeping the duplicates, closing as duplicate, and just shuffling the answers around, which is a different request.

Merge is for PERFECT duplicates.

edit: we now handle question merging in a much more sane way -- both questions are retained, one is a stub, and all answers are migrated into the merged question. If the stub is deleted, we 301 redirect to the merge target.

https://blog.stackoverflow.com/2010/06/improved-question-merging/

(nothing can be done about old merges, sadly, due to our poor choice to destroy the other question in the merge)

Previously this was impossible, as one of the merged questions (the source) was literally destroyed. A merge record is recorded in the history of the target question, but it's not in any kind of reasonably queryable format.

We now handle question merging in a much more sane way -- both questions are retained, one is a stub, and all answers are migrated into the merged question. If the stub is deleted, we 301 redirect to the merge target.

https://blog.stackoverflow.com/2010/06/improved-question-merging/

Nothing can be done about old merges, sadly, due to our poor choice to destroy the other question in the merge

replaced http://blog.stackoverflow.com with https://blog.stackoverflow.com
Source Link

Impossible at the moment, as one of the merged questions (the source) is literally destroyed -- it doesn't exist any more.

A merge record is recorded in the history of the target question, but it's not in any kind of reasonably queryable format.

It sounds to me like you're arguing for keeping the duplicates, closing as duplicate, and just shuffling the answers around, which is a different request.

Merge is for PERFECT duplicates.

edit: we now handle question merging in a much more sane way -- both questions are retained, one is a stub, and all answers are migrated into the merged question. If the stub is deleted, we 301 redirect to the merge target.

http://blog.stackoverflow.com/2010/06/improved-question-merging/https://blog.stackoverflow.com/2010/06/improved-question-merging/

(nothing can be done about old merges, sadly, due to our poor choice to destroy the other question in the merge)

Impossible at the moment, as one of the merged questions (the source) is literally destroyed -- it doesn't exist any more.

A merge record is recorded in the history of the target question, but it's not in any kind of reasonably queryable format.

It sounds to me like you're arguing for keeping the duplicates, closing as duplicate, and just shuffling the answers around, which is a different request.

Merge is for PERFECT duplicates.

edit: we now handle question merging in a much more sane way -- both questions are retained, one is a stub, and all answers are migrated into the merged question. If the stub is deleted, we 301 redirect to the merge target.

http://blog.stackoverflow.com/2010/06/improved-question-merging/

(nothing can be done about old merges, sadly, due to our poor choice to destroy the other question in the merge)

Impossible at the moment, as one of the merged questions (the source) is literally destroyed -- it doesn't exist any more.

A merge record is recorded in the history of the target question, but it's not in any kind of reasonably queryable format.

It sounds to me like you're arguing for keeping the duplicates, closing as duplicate, and just shuffling the answers around, which is a different request.

Merge is for PERFECT duplicates.

edit: we now handle question merging in a much more sane way -- both questions are retained, one is a stub, and all answers are migrated into the merged question. If the stub is deleted, we 301 redirect to the merge target.

https://blog.stackoverflow.com/2010/06/improved-question-merging/

(nothing can be done about old merges, sadly, due to our poor choice to destroy the other question in the merge)

added 68 characters in body
Source Link
Jeff Atwood
  • 310.6k
  • 107
  • 887
  • 1.2k

Impossible at the moment, as one of the merged questions (the source) is literally destroyed -- it doesn't exist any more.

A merge record is recorded in the history of the target question, but it's not in any kind of reasonably queryable format.

It sounds to me like you're arguing for keeping the duplicates, closing as duplicate, and just shuffling the answers around, which is a different request.

Merge is for PERFECT duplicates.

edit: we now handle question merging in a much more sane way -- both questions are retained, one is a stub, and all answers are migrated into the merged question. If the stub is deleted, we 301 redirect to the merge target.

http://blog.stackoverflow.com/2010/06/improved-question-merging/

(nothing can be done about old merges, sadly, due to our poor choice to destroy the other question in the merge)

Impossible at the moment, as one of the merged questions (the source) is literally destroyed -- it doesn't exist any more.

A merge record is recorded in the history of the target question, but it's not in any kind of reasonably queryable format.

It sounds to me like you're arguing for keeping the duplicates, closing as duplicate, and just shuffling the answers around, which is a different request.

Merge is for PERFECT duplicates.

edit: we now handle question merging in a much more sane way -- both questions are retained, one is a stub, and all answers are migrated into the merged question. If the stub is deleted, we 301 redirect to the merge target.

(nothing can be done about old merges, sadly, due to our poor choice to destroy the other question in the merge)

Impossible at the moment, as one of the merged questions (the source) is literally destroyed -- it doesn't exist any more.

A merge record is recorded in the history of the target question, but it's not in any kind of reasonably queryable format.

It sounds to me like you're arguing for keeping the duplicates, closing as duplicate, and just shuffling the answers around, which is a different request.

Merge is for PERFECT duplicates.

edit: we now handle question merging in a much more sane way -- both questions are retained, one is a stub, and all answers are migrated into the merged question. If the stub is deleted, we 301 redirect to the merge target.

http://blog.stackoverflow.com/2010/06/improved-question-merging/

(nothing can be done about old merges, sadly, due to our poor choice to destroy the other question in the merge)

added 343 characters in body
Source Link
Jeff Atwood
  • 310.6k
  • 107
  • 887
  • 1.2k
Loading
Bounty Ended with 250 reputation awarded by YOU
Source Link
Jeff Atwood
  • 310.6k
  • 107
  • 887
  • 1.2k
Loading