After making changes to a bug, you are told that the changes have been made, and you've caused mail to loads of people to be sent -- I think it might be nice (optionally, of course!) to have a quick summary of the changes you've just committed, to provide a bit of a sanity check that you really did make the change you tought you had. I'd think this would look similar to what is displayed on a midair collision, but probably not including the whole additional comment, just the start/end of it.
These unloved bugs have been sitting untouched since June 2002 or longer. If nobody does anything else to them, they certainly won't make 2.18 Retargetting to 2.20. If you really plan to push them right now, you might pull them back in.
This bug has not been touched by its owner in over six months, even though it is targeted to 2.20, for which the freeze is 10 days away. Unsetting the target milestone, on the assumption that nobody is actually working on it or has any plans to soon. If you are the owner, and you plan to work on the bug, please give it a real target milestone. If you are the owner, and you do *not* plan to work on it, please reassign it to email@example.com or a .bugs component owner. If you are *anybody*, and you get this comment, and *you* plan to work on the bug, please reassign it to yourself if you have the ability.
To see the changes you just made, you can always check the History. See also bug 452957 about seeing the changes you're *about* to make (which is IMHO a better sanity check). If bug 452957 gets fixed, and since the History is always available, I believe that this bug will use any usefulness it might ever have had.
Oops ...wil LOSE any usefulness...
Although the history is available, it's an extra click away, and most people are not diligent enough to take the extra effort to make sure they did something wrong. The reason why I want this feature is so that the user can tell *right away* if he made a mistakes, so that he can correct them. I disagree that this would lose usefulness if bug 452957 gets fixed, for two reasons: 1) fields are spread around all over the place, so you have to scan the whole form to see what you changed 2) it only tells you what fields changed - it doesn't compare the old value to the new value.
Also, it's useful if you're changing may bugs at the same time, then you don't need to go check the history for every bug.