From: Sergei Trofimovich <slyfox@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] toolchain-funcs.eclass / toolchain-glibc.eclass - gcc-6 bugfixes and updates
Date: Fri, 16 Jun 2017 22:38:15 +0100 [thread overview]
Message-ID: <20170616223815.7a67db62@sf> (raw)
In-Reply-To: <555cdf36-7362-2a75-f066-d6d303b90e52@iee.org>
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
On Fri, 16 Jun 2017 14:25:02 +0100
"M. J. Everitt" <m.j.everitt@iee.org> wrote:
> .. That was quick ...
>
> I swore there was something in the devmanual about a nice long period of
> bikeshedding before changes to eclasses were approved ..
The eclass writing and changes guide is described in devmanual and available
at https://devmanual.gentoo.org/eclass-writing/
Namely "Adding and Updating Eclasses" section includes rationale why one
should consider that. TL;DR: The goal is to serve both as an announcement
and as a chance to spot errors before affecting everyone.
Valuable feedback (ideally actionable or supportive) feedback is important
to community and individuals as it allows us all to make a step in the right
direction.
I view existence of bikeshedding centithreads (with zero valuable feedback)
as a negative side of Gentoo community as it's a time sink.
I suggest not to start and not to contribute to such threads.
Unfortunately even rare snarky comments don't work all that well in mailing lists.
Thanks for your patience and understanding :)
--
Sergei
[-- Attachment #2: Цифровая подпись OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2017-06-16 21:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 23:15 [gentoo-dev] [RFC] toolchain-funcs.eclass / toolchain-glibc.eclass - gcc-6 bugfixes and updates Matthias Maier
2017-06-14 23:15 ` [gentoo-dev] [PATCH 1/5] toolchain-funcs.eclass: Add functions for detection of PIE / SSP in way compatible with GCC >=6 Matthias Maier
2017-06-15 7:07 ` Michał Górny
2017-06-15 8:09 ` Matthias Maier
2017-06-15 8:11 ` Michał Górny
2017-06-15 13:45 ` [gentoo-dev] [RFC v2] toolchain-funcs.eclass / toolchain-glibc.eclass - gcc-6 bugfixes and updates Matthias Maier
2017-06-15 13:45 ` [gentoo-dev] [PATCH 01/05] toolchain-funcs.eclass: Add functions for detection of PIE / SSP in way compatible with GCC >=6 Matthias Maier
2017-06-15 14:37 ` Michał Górny
2017-06-15 14:40 ` Matthias Maier
2017-06-14 23:15 ` [gentoo-dev] [PATCH 2/5] toolchain-glibc.eclass: Build most of >=sys-libs/glibc-2.25 with -fstack-protector-all (bug #609048) Matthias Maier
2017-06-14 23:15 ` [gentoo-dev] [PATCH 3/5] toolchain-glibc.eclass: Always enable stack guard randomization (bug #621742) Matthias Maier
2017-06-14 23:15 ` [gentoo-dev] [PATCH 4/5] eclass/toolchain-glibc.eclass: use tc-enables-pie instead of gcc-specs-pie Matthias Maier
2017-06-14 23:15 ` [gentoo-dev] [PATCH 5/5] eclass/toolchain-glibc.eclass: skip pie check for gcc-6 or newer Matthias Maier
2017-06-14 23:18 ` [gentoo-dev] Re: [RFC] toolchain-funcs.eclass / toolchain-glibc.eclass - gcc-6 bugfixes and updates Matthias Maier
2017-06-16 8:27 ` [gentoo-dev] " Matthias Maier
2017-06-16 13:25 ` M. J. Everitt
2017-06-16 21:38 ` Sergei Trofimovich [this message]
2017-06-16 21:42 ` Alexis Ballier
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=20170616223815.7a67db62@sf \
--to=slyfox@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