[06:24] <christiank> Hi wgrant,
[06:25] <wgrant> christiank: Hi. No luck?
[06:25] <christiank> NO - I followed your advice to contact the SSO team with the 'Other' option and I only got the same email that I got earlier, except that it kindly noted:
[06:26] <christiank> It seems that this is the 2nd time you requested assistance via this form.
[06:26] <christiank> If you have contacted the Launchpad team, please follow their instructions.
[06:26]  * wgrant grumbles.
[06:26] <christiank> So: more going around in circles!
[06:26] <wgrant> Can you forward me the email? william.grant@canonical.com
[06:26] <wgrant> I'll follow it up internally when the SSO support people are up.
[06:26] <christiank> Thanks for that!
[06:28] <christiank> I'll stay in this channel for the next 7 or 8 hours or so, please mention my IRC nick when writing to me as this makes my IRC client issue a 'ping' sound and causes its title bar to flash, which will get my attention.
[17:46] <elijah> Is it okay to link an issue to a 'related' issue and if so is there a procedural way to do it?
[17:47] <elijah> This issue https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/749567 is related to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1321351 but is not directly a duplicate.
[17:47] <elijah> I feel like marking 1321351 as a duplicate just to get a crosslink but not sure of accepted practices
[17:54] <dobey> elijah: there's no way for a bug to have direct references to other bugs outside of duplication really. but you could simply link to the other bug in the comment by saing "This may be a duplicate of bug #XXXXX" and if it's a duplicate then someone who better understands what is going on thre can mark it so
[17:56] <elijah> dobey: Okay, that is what I did for now. Thanks