From: Mike Gilbert <floppym@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-python@lists.gentoo.org, python@gentoo.org
Subject: [gentoo-python] Re: [PATCH] Do not call the dummy no-op default phases.
Date: Tue, 8 Jan 2013 15:44:01 -0500 [thread overview]
Message-ID: <CAJ0EP43o78SNCB2wTzYDvjCZQQOi1ump4JKfBRfLJyOXZgcG0w@mail.gmail.com> (raw)
In-Reply-To: <1357677382-30391-1-git-send-email-mgorny@gentoo.org>
On Tue, Jan 8, 2013 at 3:36 PM, Michał Górny <mgorny@gentoo.org> wrote:
> This just causes a severe amount of unnecessary output.
> ---
> gx86/eclass/distutils-r1.eclass | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/gx86/eclass/distutils-r1.eclass b/gx86/eclass/distutils-r1.eclass
> index f52ffbd..fd3e856 100644
> --- a/gx86/eclass/distutils-r1.eclass
> +++ b/gx86/eclass/distutils-r1.eclass
> @@ -454,8 +454,6 @@ distutils-r1_src_prepare() {
> _distutils-r1_multijob_init
> if declare -f python_prepare >/dev/null; then
> python_foreach_impl distutils-r1_run_phase python_prepare
> - else
> - python_foreach_impl distutils-r1_run_phase distutils-r1_python_prepare
> fi
> multijob_finish
> }
> @@ -464,8 +462,6 @@ distutils-r1_src_configure() {
> _distutils-r1_multijob_init
> if declare -f python_configure >/dev/null; then
> python_foreach_impl distutils-r1_run_phase python_configure
> - else
> - python_foreach_impl distutils-r1_run_phase distutils-r1_python_configure
> fi
> multijob_finish
>
> @@ -496,8 +492,6 @@ distutils-r1_src_test() {
> _distutils-r1_multijob_init
> if declare -f python_test >/dev/null; then
> python_foreach_impl distutils-r1_run_phase python_test
> - else
> - python_foreach_impl distutils-r1_run_phase distutils-r1_python_test
> fi
> multijob_finish
>
> --
> 1.8.1
>
Makes sense.
prev parent reply other threads:[~2013-01-08 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 20:36 [gentoo-python] [PATCH] Do not call the dummy no-op default phases Michał Górny
2013-01-08 20:44 ` Mike Gilbert [this message]
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=CAJ0EP43o78SNCB2wTzYDvjCZQQOi1ump4JKfBRfLJyOXZgcG0w@mail.gmail.com \
--to=floppym@gentoo.org \
--cc=gentoo-python@lists.gentoo.org \
--cc=mgorny@gentoo.org \
--cc=python@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