From: Carsten Lohrke <carlo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Suggestion for next bugday: Mass use deps migration
Date: Mon, 23 Feb 2009 00:41:59 +0100 [thread overview]
Message-ID: <200902230042.00009.carlo@gentoo.org> (raw)
In-Reply-To: <200902222243.30071.scarabeus@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 457 bytes --]
On Sonntag, 22. Februar 2009, Tomáš Chvátal wrote:
> Well that is the reason why i am first eapi2ing the kde eclass. I was
> really suprised when i saw kde3 ebuilds with eapi2 :(
I value users suffering from package manager issues higher and fix issues as I
see them, walking through the tree. Only a handful of ebuilds are affected.
Identifying and adjusting them, when the modified eclasses hits the tree is a
quick operation.
Carsten
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-22 23:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 16:55 [gentoo-dev] Suggestion for next bugday: Mass use deps migration Petteri Räty
2009-02-22 21:34 ` Carsten Lohrke
2009-02-22 21:43 ` Tomáš Chvátal
2009-02-22 23:41 ` Carsten Lohrke [this message]
2009-02-22 21:58 ` Petteri Räty
2009-02-22 23:35 ` Carsten Lohrke
2009-03-07 14:14 ` 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=200902230042.00009.carlo@gentoo.org \
--to=carlo@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