From: "Chí-Thanh Christopher Nguyễn" <chithanh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Upcoming posting restrictions on the gentoo-dev mailing list
Date: Thu, 11 Jan 2018 18:03:27 +0100 [thread overview]
Message-ID: <32074f28-2a68-1ff6-f011-e461aa3af277@gentoo.org> (raw)
In-Reply-To: <1515578019.1284.3.camel@gentoo.org>
Michał Górny schrieb:
> I guess you should have voiced your opinion back when discussion was
> taking place instead of being hostile *now* because the Council listened
> to what the developers requested.
The arguments why these posting restrictions are a pretty bad idea have
all been voiced back then already. So no point in posting them again
each time.
But of course it is also true that Council is elected by and acts on
behalf of the developers. So my suggestion for developers who heavily
disagree with this decision is to look at who voted which way in the
public logs. Then read carefully who in their next Council election
manifesto plans to lift this restriction again.
Best regards,
Chí-Thanh Christopher Nguyễn
next prev parent reply other threads:[~2018-01-11 17:03 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 21:20 [gentoo-dev] Upcoming posting restrictions on the gentoo-dev mailing list Andreas K. Huettel
2018-01-09 22:20 ` Francesco Riosa
2018-01-09 22:27 ` Alec Warner
2018-01-10 0:37 ` Philip Webb
2018-01-10 1:24 ` Michael Orlitzky
2018-01-10 1:08 ` Matt Turner
2018-01-10 9:55 ` Michał Górny
2018-01-10 17:11 ` Matt Turner
2018-01-10 19:06 ` Michał Górny
2018-01-10 19:31 ` Alec Warner
2018-01-10 19:45 ` Michał Górny
2018-01-10 20:48 ` M. J. Everitt
2018-01-10 21:13 ` Alec Warner
2018-01-10 5:48 ` Eray Aslan
2018-01-10 7:55 ` Lars Wendler
2018-01-10 10:57 ` David Seifert
2018-01-10 13:49 ` kuzetsa
2018-01-10 14:50 ` M. J. Everitt
2018-01-15 13:26 ` Tom H
2018-01-15 15:09 ` Rich Freeman
2018-01-15 22:49 ` Gordon Pettey
2018-01-10 14:55 ` Alexander Berntsen
2018-01-10 15:09 ` M. J. Everitt
2018-01-10 15:52 ` kuzetsa
2018-01-11 7:03 ` Eray Aslan
2018-01-11 8:30 ` Lars Wendler
2018-01-10 9:53 ` Michał Górny
2018-01-10 11:14 ` Andreas K. Huettel
2018-01-10 17:16 ` Vincent-Xavier JUMEL
2018-01-10 19:44 ` Michał Górny
2018-01-11 1:12 ` Andreas K. Huettel
2018-01-11 4:22 ` [gentoo-dev] " Duncan
2018-01-11 5:37 ` Gordon Pettey
2018-01-11 8:21 ` Lars Wendler
2018-01-11 17:07 ` [gentoo-dev] " Peter Stuge
2018-01-11 17:34 ` Rich Freeman
2018-01-11 17:59 ` Matthias Maier
2018-01-13 0:02 ` Paul B. Henson
2018-01-11 14:48 ` R0b0t1
2018-01-11 17:03 ` Chí-Thanh Christopher Nguyễn [this message]
2018-01-10 19:56 ` Fabian Groffen
2018-01-10 22:28 ` Roy Bamford
2018-01-10 23:20 ` Rich Freeman
2018-01-10 23:27 ` M. J. Everitt
2018-01-10 23:35 ` Rich Freeman
2018-01-10 23:39 ` M. J. Everitt
2018-01-11 1:03 ` Andreas K. Huettel
2018-01-11 11:44 ` Roy Bamford
2018-01-11 3:22 ` [gentoo-dev] Re: [gentoo-dev-announce] " Benda Xu
2018-01-11 19:54 ` William Hubbs
2018-01-12 23:58 ` [gentoo-dev] " Paul B. Henson
2018-03-20 8:52 ` Kristian Fiskerstrand
2018-03-24 3:11 ` Francisco Blas Izquierdo Riera (klondike)
2018-03-24 3:34 ` Aaron Bauman
2018-03-25 4:07 ` Francisco Blas Izquierdo Riera (klondike)
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=32074f28-2a68-1ff6-f011-e461aa3af277@gentoo.org \
--to=chithanh@gentoo.org \
--cc=gentoo-dev@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