From: Bruno <bonbons67@internet.lu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] last rites for net-im/sim
Date: Sun, 18 Dec 2005 09:14:55 +0100 [thread overview]
Message-ID: <200512180914.55762.bonbons67@internet.lu> (raw)
In-Reply-To: <200512172055.19692.carlo@gentoo.org>
On Saturday 17 December 2005 20:54, Carsten Lohrke wrote:
> When you are interested in sim and willing to fix all bugs¹ and takeover
> maintainership) speak now. Christmas morning I'll crucify it.
>
>
> Carsten
>
>
> [1] https://bugs.gentoo.org/show_bug.cgi?id=110241
For moving over to the forked sim on berlios
(http://sim-im.berlios.de/wiki/Main_Page), is it better to keep sim masked in
portage and then continue with the forked releases once they come up, or just
restart from zero?
>From user point of view I guess the continuity option may be better...
Bruno
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-18 8:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-17 19:54 [gentoo-dev] last rites for net-im/sim Carsten Lohrke
2005-12-18 8:14 ` Bruno [this message]
2005-12-19 11:19 ` George Shapovalov
2005-12-19 17:53 ` Olivier Crete
2005-12-19 20:08 ` George Shapovalov
2005-12-19 20:59 ` Olivier Crete
2005-12-19 18:05 ` Stephen P. Becker
2005-12-19 18:58 ` George Shapovalov
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=200512180914.55762.bonbons67@internet.lu \
--to=bonbons67@internet.lu \
--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