public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Minor changes in python.eclass and distutils.eclass
Date: Mon, 05 Jul 2010 19:26:40 +0300	[thread overview]
Message-ID: <4C3207C0.2020903@gentoo.org> (raw)
In-Reply-To: <201007051818.20273.Arfrever@gentoo.org>

On 07/05/2010 07:17 PM, Arfrever Frehtes Taifersar Arahesis wrote:
> 2010-07-05 18:13:26 Samuli Suominen napisał(a):
>> On 07/05/2010 06:23 PM, Arfrever Frehtes Taifersar Arahesis wrote:
>>> These minor changes in python.eclass and distutils.eclass have been already
>>> reviewed on alias of Gentoo Python Project. It's recommended to be familiar
>>> with internals of current code before trying to understand these minor changes.
>>> Suggestions about indentation and quoting will be rejected.
>>>
>>
>> You have been already told to get rid of all the color customizations in
>> the python eclasses here:
>>
>> http://bugs.gentoo.org/show_bug.cgi?id=309057#c2
>> http://bugs.gentoo.org/show_bug.cgi?id=309057#c3
>>
>> [ .. ]
>>
>> http://bugs.gentoo.org/show_bug.cgi?id=309057#c5
>>
>> The bug was wrongly closed as fixed, as it's not really fixed before
>> it's all punted
> 
> Colors can be used with echo.
> 

Stop using echo for output and switch to standard output functions, like
einfo/eerror/elog/... like told in
http://bugs.gentoo.org/show_bug.cgi?id=309057#c5



  reply	other threads:[~2010-07-05 16:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-05 15:23 [gentoo-dev] Minor changes in python.eclass and distutils.eclass Arfrever Frehtes Taifersar Arahesis
2010-07-05 16:13 ` Samuli Suominen
2010-07-05 16:17   ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 16:26     ` Samuli Suominen [this message]
2010-07-05 16:34       ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 16:36         ` Tomáš Chvátal
2010-07-05 17:01           ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 17:38             ` Harald van Dijk
2010-07-05 17:43               ` Harald van Dijk
2010-07-05 17:55               ` Pacho Ramos
2010-07-05 18:06                 ` Petteri Räty
2010-07-05 16:37         ` Ciaran McCreesh
2010-07-05 17:02           ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 18:00         ` Mark Loeser
2010-07-05 18:29           ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 19:18             ` Mark Loeser
2010-07-05 20:23               ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 21:28                 ` Samuli Suominen
2010-07-05 21:38                   ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 21:49                     ` Samuli Suominen
2010-07-05 22:07                       ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 22:29                 ` Mike Frysinger
2010-07-05 23:31                   ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 23:37                     ` Mike Frysinger
2010-07-14 22:36                       ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 18:26 ` Petteri Räty
2010-07-05 19:59   ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 20:18     ` Petteri Räty
2010-07-05 19:37 ` Alex Alexander
2010-07-05 22:50 ` Jorge Manuel B. S. Vicetto
2010-07-05 23:18   ` Jeroen Roovers
2010-07-06  6:33     ` Petteri Räty

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=4C3207C0.2020903@gentoo.org \
    --to=ssuominen@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