On Fri, 3 Nov 2006 22:05:22 -0800
Don Armstrong <[EMAIL PROTECTED]> wrote:
> > ...It's a question of how much logging and recording
> > is enough, too much, or too little. I don't know if there's a
> > general answer, but I know how to scratch where it itches...
>
> Again, the bug log keeps the original message, and the record of what
> it did when it parsed the message. The only thing that isn't kept is
> the output of parsing the entire message to control, because that can
> affect multiple bugs, and generally isn't terribly informative anyway.
Pardon, I couldn't quite follow your second sentence above. Were you saying:
That certain output is not publicly recorded because...
1) ...KEEPING it might "affect multiple bugs".
2) ...it's prior effect can occasionally be difficult to
automatically categorize.
3) ...something else?
'1)' seems moot, since a web page copy of a sent email is not active
code, and once stored affects nothing but our eyeballs.
'2)' seems to support the opposite idea, since the larger the effect,
the more interesting and record worthy its cause.
As to whether a public html copy of a reopen confirmation email sent to
the reopener is tremendously informative, I agree it's not. The data
would only needed once in blue moon, but when needed could be a little
bit useful. It's like a 'typo' bug. Most of the time nothing very bad
happens if a typo remains, yet things are slightly better when it's
fixed.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
