From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] useq and hasq
Date: Fri, 8 Jul 2011 10:33:27 +0100 [thread overview]
Message-ID: <20110708103327.011b6582@googlemail.com> (raw)
In-Reply-To: <4E16CBEB.8020506@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 08 Jul 2011 12:20:43 +0300
Markos Chandras <hwoarang@gentoo.org> wrote:
> I believe that make them die wont improve anything but instead this
> will bring more frustration to our users. If you make them die you
> transfer the problem to the users, cause you make them file bugs and
> wait for slacking maintainers to fix the packages. I would say to
> keep the warning as it and hope that maintainers will actually step
> up and update their packages.
Uhm, no. The "make them die" would be done on an EAPI bump, so users
won't be affected.
You *do* test things before committing, right?
- --
Ciaran McCreesh
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
iEYEARECAAYFAk4WzuoACgkQ96zL6DUtXhFlfgCfeA0LdUVrx142eQn8OfMDGNLo
dtAAn3I1KYlStSLHGHpvK1qxfDldmb4c
=gj4w
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-07-08 9:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 22:21 [gentoo-dev] useq and hasq Dane Smith
2011-07-08 6:52 ` Petteri Räty
2011-07-08 7:25 ` Michał Górny
2011-07-08 8:55 ` Ulrich Mueller
2011-07-08 9:09 ` Petteri Räty
2011-07-08 9:20 ` Markos Chandras
2011-07-08 9:33 ` Ciaran McCreesh [this message]
2011-07-08 10:16 ` Markos Chandras
2011-07-08 10:19 ` Ciaran McCreesh
2011-07-08 10:29 ` Markos Chandras
2011-07-08 9:42 ` Ulrich Mueller
2011-07-08 11:16 ` [gentoo-dev] useq and hasq (RFC: eclass/ directory patch) Samuli Suominen
2011-07-08 11:40 ` Samuli Suominen
2011-07-08 12:12 ` Dane Smith
2011-07-08 15:41 ` Samuli Suominen
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=20110708103327.011b6582@googlemail.com \
--to=ciaran.mccreesh@googlemail.com \
--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