From: Ulrich Mueller <ulm@gentoo.org>
To: John Helmert III <ajak@gentoo.org>
Cc: gentoo-project@lists.gentoo.org, council@gentoo.org
Subject: [gentoo-project] Re: Council Meeting 2023-03-12: Call for Agenda Items
Date: Thu, 02 Mar 2023 03:17:10 +0100 [thread overview]
Message-ID: <ua60vc2xl@gentoo.org> (raw)
In-Reply-To: <ZAADYq9lnrwVRIzs@gentoo.org> (John Helmert, III's message of "Wed, 1 Mar 2023 20:01:06 -0600")
[-- Attachment #1: Type: text/plain, Size: 345 bytes --]
>>>>> On Thu, 02 Mar 2023, John Helmert wrote:
> Please reply with any topics you wish to be discussed during the next
> council meeting (2023-03-12).
Motion: Approve update of GLEP 68 [1,2].
Ulrich
[1] https://archives.gentoo.org/gentoo-dev/message/79647fad4c28a2f66489f0d8240b527d
[2] https://gitweb.gentoo.org/data/glep.git/log/?h=glep68
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
next prev parent reply other threads:[~2023-03-02 2:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 2:01 [gentoo-project] Council Meeting 2023-03-12: Call for Agenda Items John Helmert III
2023-03-02 2:17 ` Ulrich Mueller [this message]
2023-03-08 16:04 ` [gentoo-project] Council Meeting 2023-03-12: Agenda John Helmert III
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=ua60vc2xl@gentoo.org \
--to=ulm@gentoo.org \
--cc=ajak@gentoo.org \
--cc=council@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