[07:46] <mdke> DarkwingDuck_: no, fraid not
[07:47] <mdke> mewshi_: yep, working on Gnome desktop topics will also help Ubuntu and is a great option
[18:55] <durt> hey folks, working on a typo bug for the server guide, do I need to worry if ./scripts/validate.sh /serverguide/C/network-auth.xml returns errors regarding things I have not changed?
[19:26] <sommer> durt: with the serverguide the best way to validate is to do "./scripts/validate.sh /serverguide/C/serverguide.xml" since the serverguide files are all linked
[19:26] <sommer> durt: appreciate your help with the serverguide bugs :-)
[19:27] <durt> ah, will do. next question; what to call the diff?
[19:29] <sommer> the diff name isn't terribly important, something like network-auth.xml_typo-fix.diff would work fine
[19:33] <durt> right, validated with no errors, now to commit and post in that bug? or notify somewher eelse
[19:33] <durt> er, somewhere else?
[19:34] <sommer> yep, in the bug is fine
[19:47] <durt> hmm, the diff file is empty. I guess I missed something.. but what?
[19:52] <sommer> did you do bzr diff > file.diff ?
[19:53] <sommer> before  you committed the changes?
[19:54] <durt> no after 'bzr commit -m'
[19:54] <sommer> ah, then you'll need to do bzr diff -rlastrevno:secondtolastrevno
[19:55] <sommer> bzr help diff will give a better example if that doesn't make sense
[19:56] <durt> ok, then create a diff before commit then, the playbook is reverse.