From: "Michał Górny" <mgorny@gentoo.org>
To: Alexis Ballier <aballier@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: ban EAPI 1
Date: Thu, 11 Jun 2015 21:23:16 +0200 [thread overview]
Message-ID: <20150611212316.3100ab1f@pomiocik> (raw)
In-Reply-To: <20150611211200.21efa4d6@gentoo.org>
Dnia 2015-06-11, o godz. 21:12:00
Alexis Ballier <aballier@gentoo.org> napisał(a):
> On Thu, 11 Jun 2015 14:38:35 -0400
> Rich Freeman <rich0@gentoo.org> wrote:
> >
> > These errors are not user-visible. I really don't have a problem with
> > repoman errors for deprecated features.
> >
>
> I don't have a problem with always using --force either. But then the
> distinction between warnings and errors becomes much less clear.
Also --force disables expensive checks such as profile deptree checks.
--
Best regards,
Michał Górny
next prev parent reply other threads:[~2015-06-11 19:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 20:43 [gentoo-dev] RFC: ban EAPI 1 Ulrich Mueller
2015-06-10 20:51 ` Pacho Ramos
2015-06-10 20:55 ` Aaron W. Swenson
2015-06-10 20:56 ` Brian Dolbec
2015-06-10 21:00 ` Chris Reffett
2015-06-10 21:03 ` Michał Górny
2015-06-10 21:17 ` James Le Cuirot
2015-06-10 21:46 ` Andreas K. Huettel
2015-06-11 7:44 ` Daniel "zlg" Campbell
2015-06-11 7:56 ` Jason Zaman
2015-06-11 8:49 ` Patrice Clement
2015-06-11 9:16 ` Alexis Ballier
2015-06-11 11:04 ` Manuel Rüger
2015-06-11 11:13 ` Ulrich Mueller
2015-06-11 12:45 ` Alexis Ballier
2015-06-11 16:33 ` Ulrich Mueller
2015-06-11 16:55 ` Alexis Ballier
2015-06-11 18:38 ` Rich Freeman
2015-06-11 19:12 ` Alexis Ballier
2015-06-11 19:15 ` Rich Freeman
2015-06-11 19:26 ` Alexis Ballier
2015-06-11 19:55 ` Ulrich Mueller
2015-06-11 21:48 ` Alexis Ballier
2015-06-11 19:23 ` Michał Górny [this message]
2015-06-11 12:06 ` Mikle Kolyada
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=20150611212316.3100ab1f@pomiocik \
--to=mgorny@gentoo.org \
--cc=aballier@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