From: Torsten Veller <ml-en@veller.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Usage of vecho in the tree
Date: Wed, 27 Jan 2010 19:58:22 +0100 [thread overview]
Message-ID: <20100127195601.TA199b1.tv@veller.net> (raw)
In-Reply-To: <20100122103249.TA671f8.tv@veller.net>
* Torsten Veller <ml-en@veller.net>:
> ./dev-scheme/bigloo/bigloo-3.2b_p2.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-scheme/elk/elk-3.99.7.ebuild: vecho "Tests already run during compile"
> ./mail-mta/courier/courier-0.61.2.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./mail-mta/courier/courier-0.59.0.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./mail-mta/courier/courier-0.60.0.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./mail-mta/courier/courier-0.61.1.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./dev-libs/libmemcached/libmemcached-0.30.ebuild:vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-libs/libmemcached/libmemcached-0.30.ebuild:vecho ">>> Test phase [none]: ${CATEGORY}/${PF}"
> ./dev-libs/libmemcached/libmemcached-0.28.ebuild:vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-libs/libmemcached/libmemcached-0.28.ebuild:vecho ">>> Test phase [none]: ${CATEGORY}/${PF}"
> ./dev-lang/php/php-5.2.10.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-lang/php/php-5.2.9-r2.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-lang/php/php-5.2.10-r2.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-lang/php/php-5.2.12.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-lang/php/php-5.2.10-r1.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-lang/php/php-5.2.11-r1.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-lang/php/php-5.2.11.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-lang/mono/mono-2.4.9999.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./dev-lang/mono/mono-1.2.5.1-r1.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./dev-lang/mono/mono-1.2.6-r3.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./dev-lang/mono/mono-2.4.2.3.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./dev-lang/mono/mono-2.0.9999.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./dev-lang/mono/mono-9999.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./dev-lang/mono/mono-2.0.1-r1.ebuild: vecho ">>> Test phase [check]: ${CATEGORY}/${PF}"
> ./sys-devel/clang/clang-2.6-r1.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-python/pysvn/pysvn-1.7.0.ebuild: vecho ">>> Test phase [test]: ${CATEGORY}/${PF}"
> ./dev-python/pysvn/pysvn-1.7.0.ebuild: vecho ">>> Test phase [none]: ${CATEGORY}/${PF}"
I am going to change `vecho` to `echo` this weekend unless there are
objections.
--
Regards Torsten
prev parent reply other threads:[~2010-01-27 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 9:48 [gentoo-dev] Usage of vecho in the tree Torsten Veller
2010-01-22 10:15 ` [gentoo-dev] " Torsten Veller
2010-01-27 18:58 ` Torsten Veller [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=20100127195601.TA199b1.tv@veller.net \
--to=ml-en@veller.net \
--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