From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Query for largest msg_id?
Date: Sun, 22 May 2011 22:00:51 +0000 [thread overview]
Message-ID: <1306101513-sup-1687@masanjin.net> (raw)
In-Reply-To: <BANLkTikdq9JZbpT-DfZUNXQ74sqW2Txwqg@mail.gmail.com>
Reformatted excerpts from Horacio Sanson's message of 2011-05-20:
> Is there a way to use GMail supplied thread ids?? there is an
> extension X-GM-THRID that
> provides such information.
Not really. Heliotrope has to maintain its own message ids and thread ids.
When you feed it messages, it threads things different from how Gmail does,
anyways.
> Great I rewrote the GMail -> Heliotrope script to use the improved
> POST "/message"
> and works wonderfully.
Great!
> I am attaching the new version that is cleaner and seems to work
> without problems.
Very nice. I would like to include something like this when I release
Heliotrope to the world at large, since I suspect this will be a popular
migration path. So thank you for laying the foundation.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-05-22 22:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 15:17 Horacio Sanson
2011-05-15 15:01 ` William Morgan
2011-05-16 15:02 ` Horacio Sanson
2011-05-17 14:59 ` Horacio Sanson
2011-05-17 15:15 ` Horacio Sanson
2011-05-18 5:05 ` William Morgan
2011-05-20 15:38 ` Horacio Sanson
2011-05-22 22:00 ` William Morgan [this message]
2011-05-23 21:22 ` Hamish
2011-05-24 3:16 ` Horacio Sanson
2011-05-18 4:59 ` William Morgan
2011-05-18 20:09 ` Sascha Silbe
2011-05-19 3:14 ` Alvaro Herrera
2011-05-22 22:05 ` William Morgan
2011-05-23 7:52 ` Gaudenz Steinlin
2011-05-23 16:14 ` 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=1306101513-sup-1687@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-devel@rubyforge.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