Comment 0 for bug 106162

Description of the problem:
If someone posts a series of comments close together then quickly after marks that bug a duplicate of another (which I shall refer to as the original bug) then subscribers of the original bug will not only receive the duplication notice but they will also receive comments posted just before the duplication notice.

An example of this happening is when Bug #94290 was marked a duplicate of Bug #72018 . I received three emails:
2007-04-12 22:41 Re: [EDGY] firefox crashed [@ gtk_style_realize] [@ IA__gtk_style_attach] -- beou report
2007-04-12 22:41 Retraced Thread Stacktrace
2007-04-12 22:42 Re: /var/crash/usr_lib_firefox_firefox-bin.1000.crash (19.1)
when I should have only received
2007-04-12 22:42 Re: /var/crash/usr_lib_firefox_firefox-bin.1000.crash (19.1)
(which was the one containing
** This bug has been marked a duplicate of bug 72018
   MASTER Firefox Crash [@gtk_style_realize] [@nsFilePicker::Show]
)

Steps to reproduce:
1. Create a new bug A. Ensure you are subscribed to it.
2. Let someone else create a new bug B. Ensure you are not subscribed to it.
3. Post a series of comments to bug B.
4. Quickly Mark bug B a duplicate of bug A.

Expected results:
To receive mail that bug B has been marked a duplicate.

Actual results:
Separate mails about comments in bug B from before bug B was marked a duplicate of bug A in addition to notice that bug B has been marked a duplicate are received.