From: Olivier Crete <tester@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Lars Strojny <lars@strojny.net>
Subject: Re: [gentoo-dev] What's on with ejabberd and relatives?
Date: Thu, 02 Mar 2006 15:27:45 -0500 [thread overview]
Message-ID: <1141331266.5250.7.camel@cocagne.max-t.internal> (raw)
In-Reply-To: <1141330480.5783.1.camel@marcuse>
On Thu, 2006-02-03 at 21:14 +0100, Lars Strojny wrote:
> Am Sonntag, den 26.02.2006, 21:25 -0800 schrieb Donnie Berkholz:
> [...]
> > You might want to talk to the maintainer and herd, not all of us. Or
> > even file a bug for updates -- some people are very busy and just don't
> > notice there's a new version.
>
> Tried to talk to the maintainer, no answer for days. What would you
> suggest to do now?
Then you ask the herd.. But it seems humpback is still responsive, look
at his reply to bug #101708
--
Olivier Crête
tester@gentoo.org
Gentoo Developer
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-02 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 3:54 [gentoo-dev] What's on with ejabberd and relatives? Lars Strojny
2006-02-27 5:25 ` Donnie Berkholz
2006-02-27 6:18 ` Lars Strojny
2006-03-02 20:14 ` Lars Strojny
2006-03-02 20:27 ` Olivier Crete [this message]
2006-03-02 21:50 ` Gustavo Felisberto
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=1141331266.5250.7.camel@cocagne.max-t.internal \
--to=tester@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=lars@strojny.net \
/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