From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] Re: [gentoo-dev-announce] Re: Call for Council Agenda Items - 11-Nov-2014
Date: Wed, 05 Nov 2014 11:41:42 +0100 [thread overview]
Message-ID: <1415184102.15134.6.camel@gentoo.org> (raw)
In-Reply-To: <CAGfcS_mmV0O1J_dM60dccbYbPrSQzrNWQCf6W=EG+04ycAGSAg@mail.gmail.com>
El lun, 03-11-2014 a las 22:05 -0500, Rich Freeman escribió:
> On Sun, Oct 26, 2014 at 7:05 AM, Rich Freeman <rich0@gentoo.org> wrote:
> > The next Gentoo Council meeting is on 11 Nov 2014 at 19:00 UTC.
> >
> > The draft agenda will be updated at:
> > http://dev.gentoo.org/~rich0/council/council_agenda_20141111.txt
> >
>
> The agenda is posted at the URL above. It is not too late for
> last-minute additions. You aren't going to let us off this easily,
> are you?
>
I was wondering about making mandatory for Gentoo developers to also be
subscribed to gentoo-dev ML because a lot of stuff is discussed there
and some people look to not follow threads there until they don't
escalate to other lists or to the Council directly :/
next parent reply other threads:[~2014-11-05 10:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGfcS_kUKB-U5iggJ+ieZF+m_0n_AH4DZSqBF1qgKaQVG5LjHA@mail.gmail.com>
[not found] ` <CAGfcS_mmV0O1J_dM60dccbYbPrSQzrNWQCf6W=EG+04ycAGSAg@mail.gmail.com>
2014-11-05 10:41 ` Pacho Ramos [this message]
2014-11-05 10:43 ` [gentoo-project] Re: [gentoo-dev-announce] Re: Call for Council Agenda Items - 11-Nov-2014 Alexander Berntsen
2014-11-05 10:49 ` Pacho Ramos
2014-11-05 10:54 ` Alexander Berntsen
2014-11-05 12:33 ` Rich Freeman
2014-11-05 22:47 ` Pacho Ramos
2014-11-05 12:34 ` Andreas K. Huettel
2014-11-05 22:50 ` Pacho Ramos
2014-11-05 11:06 ` Patrick Lauer
2014-11-05 15:56 ` hasufell
2014-11-06 11:53 ` Jeroen Roovers
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=1415184102.15134.6.camel@gentoo.org \
--to=pacho@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