From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] gmail 0: messages
Date: Wed, 7 Dec 2005 20:28:44 -0500 [thread overview]
Message-ID: <ee9e417a0512071728v4b874993v4ef00afdaf52e1eb@mail.gmail.com> (raw)
In-Reply-To: <439789C3.5020501@ajft.org>
> It seems to me that Gmail (and others) seem to be using POP3 to emulate
> (badly) what IMAP is designed to do. Does anyone know why they (and
> others) choose to do this?
It's not clear to me that IMAP would help much here.
Gmail doesn't have a concept of messages being
assigned to a particular folder, so you'd only have
the inbox, and it would have a bazillion messages.
Russ
next prev parent reply other threads:[~2005-12-08 1:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 17:29 Philippe from Myrealbox
2005-12-07 18:56 ` Russ Cox
2005-12-07 20:47 ` Russ Cox
2005-12-08 1:17 ` Adrian Tritschler
2005-12-08 1:28 ` Russ Cox [this message]
2005-12-08 3:00 ` Adrian Tritschler
2005-12-08 3:59 ` Rob Pike
2005-12-08 7:36 ` geoff
2005-12-08 1:30 ` Uriel
2005-12-08 2:27 ` Adrian Tritschler
2005-12-08 2:35 ` John Floren
2005-12-09 16:13 ` David Leimbach
2005-12-09 22:56 ` Paweł Lasek
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=ee9e417a0512071728v4b874993v4ef00afdaf52e1eb@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/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).