From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org
Cc: gentoo-project@lists.gentoo.org
Subject: [gentoo-dev-announce] council meeting agenda, mar 12
Date: Tue, 7 Mar 2017 12:19:19 -0600 [thread overview]
Message-ID: <20170307181919.GA3351@whubbs1.gaikai.biz> (raw)
[-- Attachment #1: Type: text/plain, Size: 324 bytes --]
All,
The following is a draft of the council meeting agenda for Mar 12.
1. roll call
2. bugs with council involvement
3. open floor
Note: bugs with council involvement will cover the $Id$ issue unless
someone thinks we need a separate bullet point for it.
Let me know if I need to make any changes.
Thanks,
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
reply other threads:[~2017-03-07 18:20 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=20170307181919.GA3351@whubbs1.gaikai.biz \
--to=williamh@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