errito666> ericsnow: ping
<ericsnow> perrito666: hey
<perrito666> ericsnow: priv
<wwitzel3> well that 14.10 upgrade did not go well .. had to boot a live CD and do a boot repair, and now things are a bit wonky
<wwitzel3> all my dev stuff still works fine though, so that's good
<perrito666> wwitzel3: ah I got an "interesting" behavior in network for a moment
<perrito666> wwitzel3: and in the rest of my system too as you most likely saw in my attempt at a hangout yesterday
<natefinch> sinzui: reverting that merge here: https://github.com/juju/juju/pull/979
<sinzui> thank you very much natefinch .
<perrito666> natefinch: you missed the fix tag
<natefinch> dammit
<natefinch> now remind me, because I always forget... do I put that in the $$ $$ or do I have to put it in the previous commit message?  Also does it have to be 'fixes-1386766' or is it supposed to be 'fixes 1386766'  (space vs. hyphen)?
<natefinch> sinzui, perrito666 ^^
<sinzui> natefinch, fixes-1386766
<sinzui> you can optionally __fixes-1386766__ to make it bold and show the works you mean it
<natefinch> sinzui: yes, but does that work inside the $$stuff$$?  I feel like I've tried that in the past and it didn't work
<natefinch> since I think it expects just alphanumeric inside the $$ $$
<sinzui> natefinch, "$$merge$$ fixes-1386766" in the same comment is fine
<natefinch> ok
<sinzui> natefinch, and if you think CI is blocking you from merging a critical fix, add __JFDI__ to make it be tested and merged on success. __JFDI__ is our safety to ensure an automated system doesn't stop os from doing the right thing
<natefinch> ok, I thought i remembered as JFDI, but couldn't remmeber the exact syntax.  Is there documentation of this stuff somewhere?
<sinzui> natefinch, in an email to canonical-juju.
<natefinch> email is not documentation :)
<sinzui> natefinch, I can add a page to reports.vapour.ws
<natefinch> sinzui: that would be awesome, thank you :)
<sinzui> natefinch, I am not saying it is, but I write a lot of official gdocs, an no one reads them
<katco> sin