From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Last rites for net-im/kopete
Date: Thu, 12 Oct 2006 12:26:51 +0200 [thread overview]
Message-ID: <200610121226.59991@enterprise.flameeyes.is-a-geek.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
As per summary, net-im/kopete is going away (again).
For a while upstrem released some versions out of the KDE release cycle
(0.12_alpha through 0.12.2), but now 0.12.3 was merged again inside
kdenetwork-3.5.5, so the point of having it in net-im is gone again.
As I've heard the most foolish requests about this, I'll be masking it for
good. kde-base/kopete has already all the changes I did to net-im/kopete in
the past months backported, so there's no regression in moving to it now.
--
Diego "Flameeyes" Pettenò - http://farragut.flameeyes.is-a-geek.org/
Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ...
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-10-12 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 10:26 Diego 'Flameeyes' Pettenò [this message]
2006-10-27 13:43 ` [gentoo-dev] Last rites for net-im/kopete Michael Weyershäuser
2006-10-27 13:55 ` Diego 'Flameeyes' Pettenò
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=200610121226.59991@enterprise.flameeyes.is-a-geek.org \
--to=flameeyes@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