From: hiro <23hiro@googlemail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] imap4d OSX client
Date: Sun, 25 Jul 2010 15:26:21 +0300 [thread overview]
Message-ID: <AANLkTik158YtvyCvyXGLNpS3cVnde+c20VMf2dFMq1AA@mail.gmail.com> (raw)
In-Reply-To: <939ae562d66127ad16aefc5fe32a0ff3@kw.quanstro.net>
It's unfortunate that the universe isn't perfect.
What is better?
On 7/25/10, erik quanstrom <quanstro@quanstro.net> wrote:
> On Sat Jul 24 16:37:15 EDT 2010, rminnich@gmail.com wrote:
>> Thanks for that, the decision the customer used in the end was to move
>> to me.com.
>>
>> The Cloud cometh.
>
> it's unfortunate that we have better software, and don't use it.
>
> - erik
>
>
next prev parent reply other threads:[~2010-07-25 12:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 18:41 ron minnich
2010-07-24 19:10 ` erik quanstrom
2010-07-24 19:32 ` Francisco J Ballesteros
2010-07-24 20:35 ` ron minnich
2010-07-25 4:53 ` erik quanstrom
2010-07-25 12:26 ` hiro [this message]
2010-07-25 18:04 ` Andreas Eriksen
2010-07-25 19:02 ` Ethan Grammatikidis
2010-07-25 19:07 ` erik quanstrom
2010-07-25 19:07 ` erik quanstrom
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=AANLkTik158YtvyCvyXGLNpS3cVnde+c20VMf2dFMq1AA@mail.gmail.com \
--to=23hiro@googlemail.com \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).