From: "Jesús Guerrero" <i92guboj@terra.es>
To: <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Anybody using Seamonkey 2 ?
Date: Sun, 08 Nov 2009 21:47:40 +0100 [thread overview]
Message-ID: <bdce7017dcaf664c86e6d02ca15cf521@localhost> (raw)
In-Reply-To: <4AF72AC9.6080500@gmail.com>
On Sun, 08 Nov 2009 14:32:09 -0600, Dale <rdalek1967@gmail.com> wrote:
> Call me chicken, I'll wait a little bit to let them fix the bugs. I use
> almost the whole thing so I want to be sure it is safe.
If I were using the mail stuff I'd certainly do that. I would wait until I
am relatively sure that everything is going to work. For web usage it
really doesn't matter to have an occasional problem, and anyway in that
regard seamonkey 2 is going pretty well. But mail is another story. :)
In any case, if you are going to test it be sure to make backups, just in
case.
--
Jesús Guerrero
next prev parent reply other threads:[~2009-11-08 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 10:03 [gentoo-user] Anybody using Seamonkey 2 ? Dale
2009-11-08 20:00 ` Jesús Guerrero
2009-11-08 20:32 ` Dale
2009-11-08 20:47 ` Jesús Guerrero [this message]
2009-11-08 21:11 ` Dale
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=bdce7017dcaf664c86e6d02ca15cf521@localhost \
--to=i92guboj@terra.es \
--cc=gentoo-user@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