From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-project@lists.gentoo.org, gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] Call for agenda items -- Council meeting 2012-03-13
Date: Tue, 28 Feb 2012 22:11:33 +0100 [thread overview]
Message-ID: <20120228211133.GO27655@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
All,
In less than two weeks from now, the council will meet again. This is
the time to raise and prepare items that the council should put on the
agenda to vote on.
Please respond to this email with agenda items. Please do not hestitate
to repeat your agenda item here with a pointer if you previously
suggested one (since the last meeting).
The agenda for the next meeting will be sent out on Tuesday 6th of March
2012, by the chairman of the next meeting, betelgeuse.
Please respond to gentoo-project list, if possible.
--
Fabian Groffen
Gentoo on a different level
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
reply other threads:[~2012-02-29 0:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120228211133.GO27655@gentoo.org \
--to=grobian@gentoo.org \
--cc=gentoo-dev-announce@lists.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