Re: correcting bug report

David Jarvie <[email protected]>
Newsgroups gmane.comp.kde.users.pim
Message-ID <[email protected]>
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

_______________________________________________
KDE PIM users mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kdepim-users
signature.asc (application/pgp-signature, 197 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkwmURQACgkQTGZ1gSTAjlPD3ACfT1LxavRz3w6YzQ8Awle4AnPD
droAnjCp3kpCeEYTuRN5ZSDg8GKk+6qK
=HkUk
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.