Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Google and IMAP
Date: Fri, 26 Oct 2007 18:49:14 -0700	[thread overview]
Message-ID: <1193449715-sup-4100@south> (raw)
In-Reply-To: <414a99f20710240051m4656b3b6sbd0057ba95dc68a6@mail.gmail.com>

Excerpts from Tim Vaughan's message of Wed Oct 24 00:51:28 -0700 2007:
> I see here:
> http://mail.google.com/support/bin/answer.py?ctx=gmail&hl=en&answer=75725
> that Google is now rolling out IMAP access for Gmail accounts.
> I've been waiting for sup to have Gmail access before using it
> full-time - what does this development mean for sup/Gmail interaction
> now?

It means that I don't have to write a gmail bridge any more. You can
just use IMAP. Procrastination rewarded!

-- 
William <wmorgan-sup at masanjin.net>


  parent reply	other threads:[~2007-10-27  1:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24  7:51 Tim Vaughan
2007-10-24  8:47 ` Kevin Mark
2007-10-29 17:17   ` Tim Vaughan
2007-11-02  3:02     ` William Morgan
2007-10-27  1:49 ` William Morgan [this message]
2007-10-27 16:28   ` Tim Vaughan
2007-10-27 16:56     ` William Morgan

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=1193449715-sup-4100@south \
    --to=wmorgan-sup@masanjin.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