From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] council meeting agenda, mar 12
Date: Mon, 20 Mar 2017 21:13:58 -0400 [thread overview]
Message-ID: <20170321011358.GI24205@vapier> (raw)
In-Reply-To: <1489304138.1067.3.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
On 12 Mar 2017 08:35, Michał Górny wrote:
> W dniu 11.03.2017, sob o godzinie 22∶39 -0800, użytkownik Daniel
> Campbell napisał:
> > On 03/07/2017 10:19 AM, William Hubbs wrote:
> > > 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.
> >
> > Will there be an e-mail on dev-announce if the council makes a decision
> > on $Id$ and friends? I'm working during the meeting and don't want to
> > add work for others the next time I touch an ebuild.
> >
> > If there's already an easy way to find council decisions like this,
> > pardon my ignorance.
>
> The Council has already dealt with this. You'd notice if you looked
> at the code instead of just the mailing lists.
there's no need for this hostile tone and has no place here.
you could have simply answered his question.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-03-21 1:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 18:19 [gentoo-project] council meeting agenda, mar 12 William Hubbs
2017-03-12 6:39 ` Daniel Campbell
2017-03-12 7:35 ` Michał Górny
2017-03-21 1:13 ` Mike Frysinger [this message]
2017-03-12 13:33 ` Rich Freeman
2017-03-13 6:53 ` Daniel Campbell
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=20170321011358.GI24205@vapier \
--to=vapier@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