[kdepim-users] correcting bug report

[David Jarvie]

On Friday 25 Jun 2010 14:23:35 John Aldrich wrote:
> What's the best way to correct a bug report one has filed? Would you close 
> the bug report and file a new one or just update the existing report? The 
> report in question is Bug 242126 
> (https://bugs.kde.org/show_bug.cgi?id=242126)
> 
> Something is causing KMail to freeze up when I access KMail from the local 
> console after accessing it from remote via VNC over SSH. I *thought* it was 
> IMAP, but I'm no longer convinced.

It's a matter of judgement what to do. If the original bug report is really not applicable any more, you could close it as invalid and open a new one. But if it's only some details which are wrong, just add a new comment to the existing bug report. If appropriate, you can also change the bug title.

-- 
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdepim-users/attachments/20100626/d1188288/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM users mailing list
kdepim-users at kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users