From: Henrik Brix Andersen <brix@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites for media-video/helixplayer
Date: Mon, 21 Nov 2005 21:15:12 +0100 [thread overview]
Message-ID: <20051121201512.GE5876@dmz.brixandersen.dk> (raw)
In-Reply-To: <200511212029.15870@enterprise.flameeyes.is-a-geek.org>
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
On Mon, Nov 21, 2005 at 08:29:03PM +0100, Diego 'Flameeyes' Pettenò wrote:
> After realplayer the last week, also helixplayer is pending removal from the
> tree.
Please make a habit of always supplying a list of
alternates/replacements when writing a "last rites" email - saves us
someone having to ask:
What replaces it?
Regards,
Brix
--
Henrik Brix Andersen <brix@gentoo.org>
Gentoo Metadistribution | Mobile computing herd
[-- Attachment #2: Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2005-11-21 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 19:29 [gentoo-dev] Last rites for media-video/helixplayer Diego 'Flameeyes' Pettenò
2005-11-21 20:15 ` Henrik Brix Andersen [this message]
2005-11-21 20:43 ` Diego 'Flameeyes' Pettenò
2005-11-21 22:00 ` Edward Catmur
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=20051121201512.GE5876@dmz.brixandersen.dk \
--to=brix@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