----- Mensaje original ----- > On 07/08/2013 01:49 PM, Marc-André Lureau wrote: > > On Mon, Jul 8, 2013 at 6:46 PM, Marc-André Lureau > > <marcandre.lureau@xxxxxxxxx> wrote: > >> Error reported in: > >> https://bugzilla.redhat.com/show_bug.cgi?id=885200 > > Sorry, I meant https://bugzilla.redhat.com/show_bug.cgi?id=904094 > > (updated commit) > Just out of curiosity, what is the purpose of pointing a link to a bug > that is not widely accessible? Even if I am logged in in Red Hat > Bugzilla I am not authorized to see the bug. > > Sorry to pick this specific case as an example, but I've seen this quite > a few time in the virt-tools list. In the end, others don't know exactly > what was the use case of the bug, as the commit message is of no value > in this case. Sorry about that, I think many bugs should be public. Perhaps that's what we need to fix! The purpose of adding a link to the commit msg allows to track back the discussion that triggered that commit. In the bug, the error was: (virt-viewer:6515): virt-viewer-CRITICAL **: virt_viewer_display_release_cursor: assertion `klass->release_cursor != NULL' failed And it was hit when using custom key bindings to release the cursor with VNC display. _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
