From: "Tony \"Chainsaw\" Vroon" <chainsaw@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Council Meeting: Tuesday, 12th June 2012, 19:00 UTC
Date: Mon, 11 Jun 2012 21:50:46 +0100 [thread overview]
Message-ID: <1339447846.3578.60.camel@localhost> (raw)
In-Reply-To: <4FCE6657.2050108@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 433 bytes --]
On Tue, 2012-06-05 at 21:04 +0100, Markos Chandras wrote:
> The next Council meeting will be on Tuesday, 12th of June 2012 at
> 19:00 UTC[1] in the #gentoo-council channel on Freenode
Sorry to report that due to a scheduling conflict, I will have to
appoint a proxy tomorrow night. Alex "a3li" Legler will attend in my
stead. The Jubilee bank holidays caused shifts that I failed to fully
account for.
Regards,
Tony V.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-06-11 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 20:04 [gentoo-project] Council Meeting: Tuesday, 12th June 2012, 19:00 UTC Markos Chandras
2012-06-11 20:50 ` Tony "Chainsaw" Vroon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1339447846.3578.60.camel@localhost \
--to=chainsaw@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox